What it does
An EDID is how a display tells a source what it is, and on a show it's usually somebody else's, read off a screen, a scaler or a splitter, and not quite what you want. Building your own is the fix, and the tools for that are either a hex editor or a driver utility that assumes you've got a desktop monitor.
This one has two halves. Type in a resolution, a refresh rate and a name, and you get a complete, valid EDID 1.4: the mode as a detailed timing, a range-limits descriptor sized to it, the name where every input menu will read it, and a CTA-861 extension carrying the standard video code when the mode has one. Or open the advanced side and edit every field there is, including the CTA-861 and DisplayID 2.0 extensions.
The hard bit is the last one. Whether a given processor accepts a mode is rarely a straight yes or no. It depends on which input card is fitted, whether the input is set to single or dual link, whether 4K arrives on one cable or two, and what that setting costs you in inputs elsewhere. It answers that per model, naming the mode you'd need and what you'd trade for it.
- Simple mode: a resolution and a rate in, a complete EDID out
- Advanced mode: every field, including CTA-861 and DisplayID 2.0
- The minimum HDMI, DisplayPort and DVI version the mode needs
- DSC and variable-refresh as toggles that change both the arithmetic and the EDID
- Twenty-three processor models checked, each carrying its sources
- Opens a .bin or a hex dump pasted from anywhere; a bad checksum is reported, not refused
Where it stands
Published as a beta, and hosted, because there's nothing to install and nothing to upload: an EDID never leaves the tab. What's proven is the arithmetic. The timing generators reproduce published VESA values exactly, the DisplayID descriptor layout was checked byte for byte against a reference parser, and every EDID the tool builds survives a full encode-decode round trip, across eighty-two tests. What isn't proven is the part that counts in the end: no EDID this tool has made has been fed to a real processor, and the compatibility table is vendor paperwork rather than bench results. Both caveats are on the page as well as in the repository.