Parse The Data
Local only

JSON Schema validator

Test the data against the contract in the same private tab.

Data workspace

Ready in this tab

Source

0 B Processed locally
Import settingsAuto-detect enabled
JSON text

Overrides apply on the next analysis. File decoding and every transform run only in this tab.

Paste data or choose a file to begin.

Analysis canvas

Ready when you are.

  1. Add a local file or paste data.
  2. Analyze format, quality, and likely sensitive fields.
  3. Review, clean, and export the in-tab working copy.
01 / Parse

Know the shape of the data.

Detect delimiters, validate structured text, and surface useful error locations.

02 / Review

Spot quality and privacy risks.

Measure completeness, duplicates, mixed values, and likely identifiers before sharing.

03 / Prepare

Shape a working copy locally.

Filter, sort, select, rename, deduplicate by keys, validate schemas, and export without changing the original file.

Focused utilities

Start with the job in front of you.

Every route opens the same private engine with guidance tailored to that format.

CSV cleanerProfile + clean tables CSV filter + sortKeep and order rows CSV column selectorSelect + reorder fields Deduplicate by keysChoose record identity JSON validatorValidate + inspect records JSON repairFix + review syntax JSON path browserExtract RFC 6901 pointers Schema validatorTest Draft 2020-12 JSONL converterPrepare streaming data Schema generatorInfer a data contract Delimiter detectorFind hidden separators PII scannerCatch obvious exposure

Practical guide

Validate the document you actually plan to use

The same source can look different after record normalization. Choose the original JSON document when validating an API contract, or the working records when checking a transformed tabular export.

  • 01Paste valid JSON and analyze its original structure.
  • 02Open the JSON tab and select the validation target.
  • 03Paste a Draft 2020-12 schema using local # references.
  • 04Review instance and schema paths for every reported mismatch.
Can the validator fetch external $ref schemas?

No. To preserve the no-network boundary, external references are not fetched. Bundle dependencies under $defs and use local fragment references.

Does Parse The Data upload my files?

No. Parsing, profiling, cleanup, and export run inside your browser tab. The application does not send dataset contents to our server or any third party.

What file types are supported?

CSV, TSV, JSON, and JSON Lines (JSONL or NDJSON) are supported as pasted text or local files up to 10 MB. CSV files can also be decoded as UTF-8, UTF-16, or Windows-1252.

Can it detect every privacy risk?

No. The privacy scan uses deterministic patterns and column-name hints. It can find common emails, phone numbers, IP addresses, SSNs, and payment-card patterns, but it is not a substitute for a formal privacy review.

Designed for restraint

The server delivers the tools. Your dataset stays in the browser.

The app files arrive first. Parsing, profiling, and cleanup then happen in a browser worker on your device. The dataset has no upload path.

  • No accounts
  • No cloud storage
  • No third-party scripts

Use the PII scan as an early warning—not as legal advice or a compliance certification.