Build a synthetic API fixture
Generate bounded test values, use format-aware UUIDs where the schema requires them, assemble a JSON record, and validate the final payload before committing a stable fixture.
Use this converter hub when test values, spreadsheet records, API payloads, URL components, or developer units must change shape without hiding precision, quoting, encoding, or privacy boundaries. Start from the destination contract, keep an untouched source, choose the narrow tool for that representation, and validate the exported result in the real parser or importer before replacing production data.
Generate unbiased numbers and configurable unique strings for test data, with exact line, CSV, and JSON export.
Open toolConvert CSV and JSON locally with text-safe typing, strict structure checks, and protected spreadsheet output.
Open toolConvert JSON records to stable, protected CSV entirely in your browser.
Open toolConvert bases, inspect queries, calculate px/rem, transform escapes, and build commit messages in one local workbench.
Open toolGenerate 1-100 RFC 9562 UUID v4 values locally from Web Crypto with exact format options.
Open toolConvert bounded CSV or JSON records into escaped GFM tables with warnings and a real preview.
Open toolGenerate valid TypeScript interfaces or type aliases from strict JSON, locally in your browser.
Open toolConvert JSON and YAML locally with strict syntax, loss checks, and bounded YAML feature handling.
Open toolConvert exact Unix epoch units, copied logs, and zoned ISO dates locally.
Open toolParse absolute URLs or resolve references with raw, decoded, normalized, and duplicate-query views.
Open toolWorkflow guides
Use these guides when you need a concrete workflow before opening a tool.
Isolate, redact, format, and validate an API JSON body without rewriting number text or hiding duplicate keys, then check its schema separately.
Read guideConvert spreadsheet CSV exports to JSON without losing quoted cells, multiline text, leading-zero IDs, duplicate headers, or empty values.
Read guideConvert JSON and YAML configuration files while checking duplicate keys, number precision, comments, anchors, aliases, multi-document streams, and destination schemas.
Read guideIsolate a useful HTML fragment, convert its syntax to JSX, review active code and parser changes, then integrate and test it as a real React component.
Read guideTool selection guide
| Tool | Best for |
|---|---|
| Random Data Workbench | Numbers and Test Strings | Generate bounded numbers and labeled strings for fixtures without copying production records, then export exact lines, CSV, or JSON. |
| CSV to JSON and JSON to CSV Converter | Local and Loss-Aware | Move quoted tabular records between CSV and JSON while reviewing headers, types, empty cells, and spreadsheet-safe output. |
| Developer Conversion Workbench | Query, CSS, Escape, Base, and Commit Tools | Convert exact integer bases, inspect ordered query data, calculate px/rem values, escape strings, or assemble a commit message. |
| URL Encoder and Decoder | Exact Percent Encoding and Plus Rules | Apply explicit component, full-URL, or form encoding rules without confusing plus signs or decoding nested layers repeatedly. |
Recommended workflows
Choose a workflow from the destination you need, not from a vague conversion label. Keep the original beside the result, make one transformation at a time, and verify type, encoding, order, and precision at every handoff.
Generate bounded test values, use format-aware UUIDs where the schema requires them, assemble a JSON record, and validate the final payload before committing a stable fixture.
Inspect the JSON structure, convert records to or from quoted CSV, review union columns and empty values, and test the exact file in the destination importer.
Inspect ordered query entries, apply the correct URL encoding profile once, and keep integer or unit conversion separate from string escaping so each result can be checked.
FAQ
Record both, but choose settings from the destination parser contract. CSV quoting, JSON numeric limits, URL component rules, database decimal scales, and fixture schemas can reject a result that looks correct in plain text.
The priority workflows are designed for browser-side processing. Review each tool boundary, decline analytics when desired, and never assume that a local tool makes copied production data appropriate to paste or share.
Fixture work changes a documented schema into safe synthetic examples and then exports them as lines, CSV, or JSON. It belongs in the same handoff workflow while remaining separate from password, token, and production-data anonymization systems.
Use the workflow when a task crosses representations, such as generating fixture values, assembling JSON, converting records to CSV, and validating an importer. For one exact encoding or numeric change, open the narrow tool directly.