Ventoy Ignores ventoy.json Fix JSON Errors and Validate Your Config
Default theme, raw file names, missing aliases - and no error anywhere. One syntax mistake makes Ventoy ignore your entire ventoy.json. Here are the five classic mistakes and the validation route that proves the file is healthy.
By Technical AnshuVentoy Theme Guide7 minute read
Watch the video to see the settings file the video's setup depends on
Here is Ventoy's most silent failure: you edit ventoy.json, boot the stick, and nothing you set exists - default theme, raw file names, no aliases. No error, no warning. The cause is almost always one syntax mistake in the JSON, because a settings file Ventoy cannot parse is a settings file Ventoy ignores. This guide lists the classic mistakes, shows the clean fix route, and ends with the two ways to validate the file for certain.
Ventoy behaviourwhole file ignored, no error shown
Menu resultfactory defaults everywhere
A single trailing comma is enough - JSON is strict, and Ventoy responds to a broken file by quietly using defaults
1
The Five Classic Mistakes
Trailing comma after the last item in a block, as in the panel above
Smart quotes - the file was edited in Word or pasted from a chat, and straight quotes became curly ones; JSON only accepts straight " quotes
Backslash paths typed the Windows way - every path in ventoy.json uses forward slashes, like /ventoy/theme/mytheme/theme.txt
Single quotes around names or values - JSON requires double quotes everywhere
The .txt trap - Windows Notepad saved the file as ventoy.json.txt with the extension hidden, so the real ventoy.json is an old file (or does not exist) while your edited copy sits next to it unread
2
Fix the File in a Plain Text Editor
Open the file from ventoy/ventoy.json on the drive in Notepad or any code editor - never a word processor
Turn on show file extensions in Explorer and confirm the name is exactly ventoy.json
Remove trailing commas, replace any curly quotes with straight ones, and convert path backslashes to forward slashes
Save as plain text, UTF-8 - most editors do this by default; if yours offers a format choice, never pick rich text
Too tangled to trust? Let VentoyPlugson rewrite it: open Plugson, make one small change in any panel and save - the file is regenerated in clean JSON, then re-apply your theme choice
3
Validate at Boot with the F5 Check Screens
Boot the stick, press F5 and open Tools - Check plugin json configuration. There is a check screen per plugin - global control, theme, menu alias, menu class and the rest. Each shows the values Ventoy parsed from your file for that boot. If a section shows your settings, that part of the file is valid and live. If a section is empty or reports a problem while your file clearly contains those settings, the file still has a syntax error somewhere above that section - JSON parsers stop at the first error, so everything after it is invisible too.
4
The Safe Reset When Nothing Works
If the file is a mess and you need the stick working now, delete ventoy.json (or rename it to ventoy-old.json). With no settings file, Ventoy boots with complete factory defaults - every ISO still listed and bootable, because settings never touch the ISO files themselves. Then rebuild the settings calmly: open Plugson, re-select your theme, re-add aliases, and save. Rebuilding a clean file from defaults is faster than hunting one invisible character through a broken one.
Work rule for every future edit: change one thing, save, boot, check. A ventoy.json built in small verified steps never needs the reset - and when a step does break, you know it was the last change you made.
Watch the Full Setup in the Video
The video creates the setup this fix protects - worth a rewatch after repairing the file.
Why does Ventoy show no error when ventoy.json is broken?
By design, a missing or unreadable settings file simply means default behaviour - the same as a fresh stick. That makes Ventoy robust, but it also means a syntax error fails silently. The F5 Check plugin json configuration screens exist precisely so you can see what was actually parsed.
Can a broken ventoy.json stop my ISOs from booting?
No. The settings file only controls appearance and plugin behaviour. Even if you delete it completely, Ventoy lists and boots every ISO on the drive with factory defaults. Your files are never at risk from a config mistake.
What is the fastest way to get a guaranteed-valid ventoy.json?
Let VentoyPlugson write it. Open Plugson, set your theme and any other options in the panels, and save - Plugson generates strict JSON for you. Hand-editing is fine for small changes, but Plugson removes the whole class of syntax errors.
This guide is based on the Ventoy Custom Wallpaper Setup video by Technical Anshu - Add Your Branding - Stuck on a step? Ask in the video comments, help is always there.