JSON to Python Dict Converter

No. The conversion runs entirely in your browser using client-side JavaScript, so your data never touches a server and never leaves your device. That makes it safe for config files, API responses and other sensitive payloads.

They map to Python's True, False and None respectively. This is the core reason raw JSON is not directly valid as a Python literal: Python capitalizes its booleans and uses None instead of null.

Either is valid Python. Single quotes are the more common convention and the default here, matching tools like Black. Pick double quotes if your project standardizes on them or if your strings frequently contain apostrophes.

Yes. Backslashes are doubled, the active quote character is escaped, and newlines, carriage returns and tabs inside strings become the \n, \r and \t sequences. The result is a literal that Python parses without a syntax error.

No. The output is Python source, not JSON, because of True, False, None and single quotes. To read it back at runtime use ast.literal_eval, which safely parses a Python literal, or paste it straight into your code as a value.

A JSON array at the top level becomes a Python list rather than a dict. Every element is rendered recursively, so nested objects inside the array still turn into dicts with the same indentation rules.

Each level of nesting adds the indent width you chose (2 or 4 spaces). Dicts and lists print one entry per line with a trailing comma, which keeps deep structures readable and produces clean diffs in version control.

The tool tries to parse the input first. If it is not valid JSON, you get an error message describing the problem instead of a broken literal, so you can fix the source before copying.

Numbers pass through as their JSON text form, so 1.5 stays 1.5 and 42 stays 42. Python and JSON share the same numeric syntax for these cases, so no conversion is needed.