The integer that changed before you touched it
9007199254740993 is valid JSON. A familiar parser can still change it. Inspect the number token before trusting the round trip.
Worked example includedA closer look at your data
Inspect data.
Find the mismatch.
Five focused tools. Clear inputs, explainable outputs. All in your browser.
Local by default. Always.Your input stays on this device.
01 / STRUCTURED DATA
JSON Inspector
Give your data some structure. Keep every number intact.
Nothing silently discarded. Duplicate keys are rejected. Number tokens retain their original precision, including integers beyond JavaScript’s safe range. Object order is preserved.
02 / FOLLOW THE CHANGE
JSON Compare
Two documents. Every added, removed, and changed path.
Changes by path
Arrays compare by index. An insertion can change subsequent indexes; there is no identity matching. Object key order is ignored. Numbers compare by exact mathematical value (1 equals 1.0). Paths use JSON Pointer: ~0 means ~ and ~1 means /. Duplicate keys are rejected.
03 / ENCODING BOUNDARIES
URL Workbench
See the parts. Choose exactly what gets encoded.
URL parts & query
Whole URL ≠ component. Whole-URL operations preserve reserved delimiters; component operations encode them. Query parsing preserves repeated keys and treats + as a space. Component decoding keeps + literal. URL parsing may normalize hostnames and paths; it never fetches a URL.
04 / BYTES, MADE VISIBLE
Base64 Lab
Encoding is a representation. It is never encryption.
Read on this device. Never uploaded. Maximum 2 MiB.
No file selected.
Text and bytes are different. Text uses UTF-8; invalid UTF-8 is rejected. Binary decoding shows a hex preview and downloads the original bytes. Standard padded Base64 only; ASCII spaces and line breaks are allowed. URL-safe Base64 is not accepted. Files and decoded data: 2 MiB maximum; encoded input: 4 MiB maximum.
05 / REMOVE THE GUESSWORK
Timestamp Explorer
The same digits can mean very different dates.
Interpreted in your selected timezone.
Time, explicitly
Units are never guessed. All outputs share one millisecond base value. Seconds support three decimal places; milliseconds are integers. ISO output is always UTC. Local time follows this device’s timezone; repeated daylight-saving times use the earlier occurrence. Leap seconds are not represented.
Runs on your deviceNo eval. No AI. Just your data.
A CLEARER PROCESS.
A SMALLER FOOTPRINT.
Your browser is the workbench.
Processing happens on your device. No uploads, account, or external services.
Errors should explain themselves.
Find the line, follow the path, and see the rule. Your original input stays intact.
Inspect data. Never execute it.
No eval, no user code execution, and no input sent to an AI model.
THE FIELD NOTES
The details that make a difference.
Small experiments. Expected outputs. Fewer surprises in production.
The ampersand that became a second parameter
Whole URLs and query values have different encoding boundaries. Keep separators separate from the text you meant to send.
Worked example includedWhy one array insertion can produce three changes
An index-based comparison answers what changed at each position. Walk through an insertion before treating every changed path as a new record.
Worked example includedBase64 changes the envelope, not the secret
Follow UTF-8 text into Base64 and back, then decode bytes that are not text. No key, no secrecy, no silent replacement characters.
Worked example includedOne greeting, three different ideas of length
A string’s visible characters, UTF-16 code units, and UTF-8 bytes answer different questions. Inspect the boundary with one emoji.
Worked example includedA timestamp without a unit is only half a value
Seconds and milliseconds can both look plausible. Make the unit and timezone explicit before interpreting a release event.
Worked example included