What Is EDID? Why Swapping a Monitor Can Kill the Picture

EDID in one sentence

EDID (Extended Display Identification Data) is a block stored inside the display that tells the source "what I am and which resolutions and timings I support". The source reads it and only then outputs a format the display can accept.

The mechanism is a good thing: it lets one source work with CRTs, LCDs and everything since, because EDID carries a generic description of virtually all display parameters, not just resolution.

What the 128 bytes contain

The base EDID block is 128 bytes, laid out as follows (EDID 1.3):

Bytes	Field	Notes
0–7	Header	Fixed 00 FF FF FF FF FF FF 00; identifies the block as EDID
8–9	Manufacturer ID	Three-letter vendor code, packed
10–11	Product ID	Vendor-assigned product code
12–15	32-bit serial number	Unique identifier
16–17	Manufacturer info	Week and year of manufacture
18–19	EDID version	e.g. 1.3, 1.4
20–24	Basic display parameters	Power features, maximum height and width
25–34	Colour characteristics	Chromaticity coordinates driving colour reproduction
35–37	Established timings	Most basic timings and resolutions
38–53	Standard timings	Standard resolutions and timing information
54–125	Detailed timings	Four 18-byte detailed timing descriptors
126	Extension flag	Ignored in EDID 1.3; set to 0
127	Checksum	Sum validation byte

Worth noting: a bad checksum invalidates the entire block, and the source falls back to its most conservative output — often 640×480 or nothing at all. This is not rare with non-standard displays or home-made cables.

How it is read: the DDC channel

EDID travels over the DDC (Display Data Channel) between the display and the graphics adapter. It uses dedicated low-speed pins in the HDMI/DVI connector, physically separate from the high-speed lanes that carry the picture.

• Cable quality therefore matters: a broken high-speed lane gives you snow; a broken DDC lane gives you "no EDID" — a completely blank screen that a new cable fixes instantly.
• More visible over distance: DDC is unamplified and slow. An extender or fibre kit that forwards only the high-speed lanes leaves the far end unable to read the display.

Four typical negotiation failures

Symptom	Possible EDID cause
No signal at all; display reports "no input"	EDID never read; the source refuses to output
Resolution stuck at a very low value	A conservative EDID read, or fallback after checksum failure
Picture fine but no audio	The audio capability block was not parsed correctly (common with converters)
Works on another display	The two EDID blocks differ; the source handles one but not the other

Isolation: not read, or read wrong

1. Swap the cable first: cheapest way to rule out the DDC path.
2. Test direct: source straight to display. Direct works, through-device fails → the intermediate device mishandles EDID.
3. Compare with another display: separates a bad EDID block from a source that parses incorrectly.
4. Force a resolution: manually set a format both ends support, bypassing negotiation. A picture confirms the fault is in negotiation.
5. Read the actual EDID: use OS display settings or a dedicated tool to dump it and sanity-check vendor ID, version and detailed timings.

Solving it in practice: EDID management

On matrices, splitters, extenders and encoders, how EDID is handled decides compatibility. There are three common strategies:

• Pass-through: forward the sink's EDID unchanged. Accurate, but if the display powers off or is unplugged the source loses EDID and re-negotiates, briefly dropping the picture.
• Built-in / fixed EDID: the device always reports the same preset block regardless of what is connected. Stable and immune to hot-plug, but a mismatch between preset and actual capability causes wrong resolution or no picture.
• EDID learning / copy: read the target display's EDID once, store it, then keep using it. This is the usual compromise in real projects — adapted to the real display, and no re-negotiation on hot-plug.

EDID vs HDCP — do not confuse them

Both live on HDMI auxiliary channels and both can produce "no picture", but the mechanisms are entirely different:

	EDID	HDCP
Purpose	Capability negotiation (what I support)	Content protection (are you authorised)
When it fails	At connection setup	Continuously, every 2 seconds
Typical symptom	No signal or wrong resolution	Protected content black or degraded
Depends on content?	No — same for any clip	Only protected content

Quick separation: replay local unprotected content. If the symptom is unchanged, investigate EDID; if it disappears, investigate HDCP.