What can the repair function fix?

Unambiguous mistakes such as trailing commas, JavaScript-style comments, single quotes, unquoted keys, Python literals (True/False/None), leading zeros or + signs, and missing commas between values. The repaired result aims to be strictly valid JSON.

Why do I see a JSON path next to each error?

The path (for example root.settings.mods[2]) shows where in the data structure the problem sits, which is faster to fix in large DayZ config files than a line number alone.

Is my JSON uploaded anywhere?

No. Validation, repair and formatting run entirely in your browser. DayZDB does not upload, store, or send your JSON content to a server.

Does valid JSON guarantee DayZ will accept the file?

No. Valid JSON only means the syntax is correct. Mods and servers can still reject unknown keys, wrong types, or schema mismatches. Treat this tool as a first pass before testing in-game.

Tools · Config

DayZ JSON Validator

Paste JSON or open a file: the validator scans the whole document in one pass and lists every error with position, JSON path, and a plain-language explanation. Common mistakes (trailing commas, comments, single quotes, unquoted keys, Python literals) can be repaired with one click — entirely on your device.

Private by design. Your JSON stays in this browser tab. Nothing is uploaded to DayZDB, analytics, or third-party APIs. No account is required.

Indent Sort keys

Drag & drop a .json file anywhere on the editor

What this tool checks

Strict JSON syntax for DayZ configs and mods — with repair for common non-JSON habits.

DayZ server owners and modders often keep settings in JSON: launcher profiles, mod configs, Discord bots, and tooling exports. A trailing comma, a // comment, or a Python True can break parsers that expect strict JSON. This validator lists every structural problem it can see in one pass, with line, column, and a JSON path such as root.mods[3].name.

Repair is optional and explicit: it rewrites unambiguous mistakes into valid JSON. Format and Minify pretty-print or compact the document (optionally sorting keys). Neither claims the file matches a DayZ schema.

Related DayZDB tools: XML Validator for Central Economy XML, Types Editor for types.xml, and CE types for loot values.

FAQ

Common questions about validating DayZ-related JSON.

What can the repair function fix?: Everything with an unambiguous interpretation: trailing commas, JavaScript-style comments, single quotes, unquoted keys, Python literals (True/False/None), leading zeros or + signs, missing commas between values, and more. The repaired result aims to be strictly valid JSON.
Why do I see a JSON path next to each error?: The path (e.g. root.settings.mods[2]) tells you where in your data structure the problem sits — much faster to fix in large config files than a line number alone.
Is my data uploaded anywhere?: No. Validation, repair and formatting run entirely in your browser, and your JSON never leaves your device.
Does valid JSON guarantee that DayZ will accept the configuration?: No. Well-formed JSON is necessary but not sufficient. Wrong keys, types, or mod-specific schemas can still fail at runtime. Always verify in a test environment after structural checks pass.