INPUT
Click to start typing
or drag & drop a file, or use 📂 above to browse
OUTPUT
Output will appear here after conversion.
Convert between data formats instantly — JSON, XML, CSV, YAML, Base64, Hex, Markdown, Binary, Morse and more. 100% client-side, nothing leaves your browser.
If you've ever needed to transform a chunk of JSON into CSV for a spreadsheet, or convert an XML API response into YAML for a config file, you know how tedious manual reformatting can be. CodeForge handles that in seconds. Pick your input format, pick your output format, paste your data, and convert.
The tool supports 15 formats in total: JSON, XML, CSV, YAML, TOML, Base64, Hex, Binary, Octal, Markdown, HTML, Morse Code, SQL INSERT, URL Encoded, and ASCII Codes. That covers a surprisingly wide range of real scenarios — from reformatting API payloads to preparing data for database imports, to converting documentation between Markdown and HTML.
What makes this different from other converters? Everything runs in your browser. Your code, your config files, your API responses — none of it gets transmitted anywhere. You can safely paste production data without worrying about it ending up on someone else's server.
CodeForge is a client-side application. The conversion logic — parsing, reformatting, beautifying — all runs inside your browser using JavaScript libraries loaded locally. There's no backend server, no API endpoint, and no database storing your conversions.
This means you can convert sensitive configuration files, internal API responses, or proprietary data structures without any risk of exposure. Even the YAML and CSV parsing libraries ship with the page itself rather than loading from a CDN at runtime.
Yes. When converting JSON to CSV, CodeForge flattens nested objects into dot-notation column headers. An object like {"user": {"name": "Jo"}} becomes a column called user.name. Arrays of objects work too — each object becomes a row.
Since everything runs in your browser, the limit depends on your device's available memory. Most modern browsers handle files up to 10-50 MB without issues. For very large files (100MB+), you may notice slower processing or memory warnings. If that happens, try splitting the file into smaller chunks first.
The output is formatted for readability by default. JSON gets pretty-printed with proper indentation, XML is nicely nested, and CSV preserves clean column alignment. If you need minified output, you can always strip whitespace after copying. The primary goal here is producing clean, human-readable conversions.
CSV is inherently a flat format — rows and columns, no hierarchy. When you convert nested JSON to CSV, the tool flattens it by creating dot-notation column headers. So {"user": {"name": "Milan", "address": {"city": "Ambernath"}}} becomes columns like user.name and user.address.city. Arrays get indexed: items.0, items.1, etc. It works well for moderately nested data, but if your JSON is 10 levels deep with mixed arrays, the resulting CSV might have hundreds of columns — at that point, XML or YAML might be a better target format.
Yes, the tool parses your JSON input and flags syntax errors with specific details. Missing commas, unclosed brackets, trailing commas after the last item — you'll see exactly what's wrong and where. Fix the error and try again. It's faster than scanning through hundreds of lines of raw text looking for a single misplaced character, and you get the validation for free as part of the conversion process.
JSON doesn't support comments at all — it's not part of the specification. So when you convert YAML (which does support comments with the # symbol) to JSON, all comments are stripped. If you need to preserve notes and annotations, consider converting to TOML instead, which supports comments natively. Alternatively, you can add your comments as descriptive key-value pairs in the JSON output.
Yes, the tool parses SQL INSERT syntax and extracts the values into a flat table format. Column names come from the INSERT statement's column list. This is useful when you need to review database seed data in a spreadsheet, share test data with someone who doesn't have database access, or quickly visualize what your migration scripts are actually inserting.
Fields containing commas, double quotes, or newline characters are automatically wrapped in double quotes following the RFC 4180 standard. Existing double quotes inside field values are escaped by doubling them (so one quote becomes two). The output is always standards-compliant CSV that any spreadsheet application — Excel, Google Sheets, LibreOffice — can import correctly without manual cleanup.
Further reading and related converters on ZeroDataUpload: