8KDVD Menu Maker: Building Disc Menus That Switch Resolutions
8KDVD menus are HTML and JavaScript living on the disc, not a proprietary Blu-ray HDMV project. Menu Maker exists for authors who want control: background art, chapter entries, and – critically – buttons that switch between 8K, 4K, HD, and optional 3D bitstreams without leaving the launcher. Get the links wrong and users will swear the format is broken when you simply advertised a file you never encoded.
What Menu Maker produces
The tool builds the navigation layer consumed by the Universal Web Launcher and the Windows Player. Output is a menu folder: HTML entry points, assets, and wiring to your Video File Maker tiers. Smoke-test that folder in Chromium on the hard drive. If the menu fails locally, burning will not fix it.
Build workflow
- Clone or download 8KDVD-Menu-Maker from GitHub.
- Point it at the encoded video tiers from Video File Maker (HQ Plus / HQ / Standard / LP outputs as applicable).
- Set background art – stills around 3500 px wide or wider keep large displays from looking soft.
- Enter title text and button labels your audience will understand (“Play 4K”, not internal filenames).
- Enable only the resolution variants you actually produced. No 8K button without an 8K file.
- Add chapter names that match real access points in the encode when the menu supports them.
- Export the menu folder into the disc structure beside the media files.
- Open the menu HTML in Chromium; click every button once.
- Wrap with ImgBurn as UDF 2.60 or drop the folder into your ISO build.
Resolution switching without surprises
Multi-resolution discs are the format’s everyday flexibility: one red case, several decode targets. The menu is the contract. If Standard encode only produced 4K and HD for a long feature, the 8K button should stay off. Conversely, a short HQ Plus demo may ship 8K + 4K and omit LP entirely. Document the available tiers on the packaging back so retail browsers know what the plastic contains.
Design habits that save support mail
- Keep the first screen sparse: Play, Resolutions, Chapters, Credits.
- Use high-contrast text over busy key art; living-room viewing distance is not a desktop.
- Test HDR titles with the Windows HDR path and SDR titles with HDR off – menu chrome should remain readable either way.
- Ship launchers for the platforms you claim; do not bury
index.htmlfive folders deep without a starter.
Browser reality check
Because navigation is web tech, behaviour tracks Chromium more than a Hollywood player SoC. Local file permissions, autoplay policies, and GPU decode limits all show up as “menu bugs.” Prefer the Windows Player for demos; keep the HTML path as the cross-platform fallback (Windows, macOS, Linux, Android). Watch the master tutorial linked from the official authoring guide when the UI fields feel opaque – fifteen minutes of that footage beats guessing button IDs.
When something misbehaves, isolate layers: broken art path vs wrong media URL vs player chrome. Swap in a plain coloured background; if buttons suddenly work, your asset path was wrong. If Play still fails, the menu is fine and the bitstream path is not. Keep a known-good sample ISO from the project site as a control disc so you can tell “my menu” from “this PC cannot decode VP9 at 8K.”
Downloads and the living authoring guide are on 8kdvd.hddvd-revived.com. Menu Maker is half the modern toolchain; pair it with Video File Maker and only then argue about box art.



