Tool · runs in your browser

TranslucentTB settings.json validator

Q: Where do I see TranslucentTB's own error?

Right-click the tray icon, then Advanced › Open log file. Errors are logged at the default "warn" verbosity, so the deserialization error is in the log without changing anything.

Q: Does the validator know about every setting?

It knows every key TranslucentTB 2026.2 reads, including copy_dlls and use_xaml_context_menu, which are not in the official schema description. Keys it does not know are listed as ignored, which is also what the app does.

If TranslucentTB ignores your settings, one value in the file is usually wrong, and the app has quietly loaded defaults for everything. Paste the file here to see exactly which line, with the message TranslucentTB 2026.2 logs.

By translucenttb.devUpdated October 29, 2026Checked against TranslucentTB 2026.2 Tested hands-on on Windows

settings.json

Open file

Nothing is uploaded. The check runs on this page.

Waiting for a file

Paste settings.json on the left. Results update as you type.

What the validator checks

It reproduces the parser in TranslucentTB 2026.2 (ConfigManager::LoadFromFile and the Deserialize functions in Common/config), so the first error it reports is the one TranslucentTB writes to its log. It also adds hints the app does not give.

For example, these are the real dialogs TranslucentTB showed in our Windows test. The validator reports the same messages, with the line number.

Real screenshot · TranslucentTB 2026.2 · Windows build 26100The real dialog for "accent": "Acrylic" (capital A). TranslucentTB then uses defaults for every setting.
How this was captured
Captured October 29, 2026 on Windows build 26100 in our hands-on test; only cropped and resized. Settings used:
`{ "desktop_appearance": { "accent": "Acrylic", "color": "#00000000" } }`

Real screenshot · TranslucentTB 2026.2 · Windows build 26100The real dialog for a missing comma in settings.json.
How this was captured
Captured October 29, 2026 on Windows build 26100 in our hands-on test; only cropped and resized. Settings used:
`{ "desktop_appearance": { "accent": "clear", "color": "#00000000" } "oops": 1 }`

Check	What TranslucentTB does	Result
JSON syntax	Parses with comments (`//`, `/* */`) and trailing commas allowed. Single quotes, missing commas or unclosed strings fail.	All settings reset
Wrong type	`"true"` (a string) where a boolean is expected, a number in quotes, an object where a list is expected.	All settings reset
Unknown accent or verbosity	Values are case-sensitive: `"Acrylic"` and `"Blur"` are invalid.	All settings reset
Invalid color	Must start with `#` and have 3, 4, 6 or 8 hex digits. Alpha is the last pair.	All settings reset
Invalid language	Must look like `de` or `de-DE` (lowercase language, uppercase region).	All settings reset
Unknown key	Logged at "info" level and skipped. Typos like `"blur_raduis"` silently do nothing.	Key ignored
blur_radius above 750	Capped at 750 (a Direct2D limit).	Value changed
Empty file	Treated as "no settings": defaults, no error.	Defaults

Questions

Why did TranslucentTB reset all my settings?

Because it validates the whole file at once. When any value fails, it shows a dialog titled "TranslucentTB … - Error" that says TranslucentTB has encountered an error. Failed to deserialize JSON document followed by the detail, writes the same text to its log, and loads the default for every setting, not only the broken one. Your file on disk is not changed until the app saves settings again, so fix the line the validator shows and save.

Where do I see TranslucentTB's own error?

Right-click the tray icon, then Advanced › Open log file. Errors are logged at the default "warn" verbosity, so the deserialization error is in the log without changing anything.

Does the validator know about every setting?

It knows every key TranslucentTB 2026.2 reads, including copy_dlls and use_xaml_context_menu, which are not in the official schema description. Keys it does not know are listed as ignored, which is also what the app does.

My file passes but the taskbar still does not change.

Then the file is fine and the cause is elsewhere: a disabled state, a state with higher priority winning, or TranslucentTB not running on that taskbar. See dynamic modes and troubleshooting.

Keep going

Settings builderDesign every taskbar state on your own wallpaper, export settings.json.settings.json referenceEvery key, type and default, checked against the source.TroubleshootingEvery error message and common problem, with fixes.

Something wrong or out of date? Email hello@translucenttb.dev and we will fix it.