escentmachine / the developer workbench
A precise workspace for JSON, URLs, encoding and time.
01 / STRUCTURED DATA
See the structure. Keep the exact numbers.
Your inspected JSON will appear here.Precision policy Number tokens stay exact. Duplicate keys are rejected, never overwritten. Strict JSON: no comments or trailing commas. 1,048,576 code units · 128 levels · 50,000 values.
02 / STRUCTURAL DIFFERENCES
Follow each change to its object path.
Comparison rules Object key order is ignored. Arrays compare by zero-based index, so inserting an item shifts later comparisons. Numbers compare as exact decimals (1e3 equals 1000). Duplicate keys are rejected. Up to 1,000 differences are displayed and copied.
03 / ENCODING BOUNDARIES
A whole URL and a query value are different jobs.
Parsed fields will appear here.
Query rules Repeated parameters keep their order. In queries, + means a space and %2B means a literal plus. Paths and fragments remain encoded. HTTP(S) only; browser URL normalization applies.
04 / BYTES, NOT SECRETS
Keep text encoding separate from binary data.
Maximum 2 MiB. Read in memory; never uploaded.
No file selected.
Encoding, not encryption Base64 is reversible and does not protect secrets. ASCII whitespace is ignored when decoding. Standard padding and unused bits are validated. Invalid UTF-8 is rejected in text mode; use binary mode to keep the bytes. 2 MiB byte limit.
05 / TIME WITHOUT GUESSWORK
Pick the unit. Pick the timezone. See the instant.
Seconds since 1970-01-01T00:00:00Z. Up to 3 decimal places.
An explicit unit prevents a thousandfold misunderstanding.
THE SAME INSTANT
Your date and timestamp results will appear here.
Time model Unix epoch milliseconds are the normalized base unit. Seconds accept up to 3 decimals; milliseconds must be integers. No silent rounding, unit guessing or leap seconds. Invalid and ambiguous local calendar times are rejected. Local timezone comes from this browser.
The input is the source of truth.Exact tokens. Explicit units. No silent fixes.
Errors should explain themselves.A location, a reason, and a useful next step.
Your data stays on your machine.No storage, tracking, or processing requests.
FIELD NOTES / ACCURACY FIRST
Know why the result looks that way, with examples you can run.
An empty array contains no elements; an empty object contains no named members. Check JSON parsing, container type, and emptiness separately, then verify the…
Read field note : How to Tell an Empty JSON Array From an Empty ObjectJSON number syntax determines which spellings are permitted. Learn why 012 and 0x10 fail, why fractional and exponent zeros work, and how to choose…
Read field note : Why JSON Rejects Leading Zeros and Hexadecimal NumbersInspect a prefixed response without losing the original evidence. Confirm the endpoint’s exact prefix, remove it once from a working copy, and parse the…
Read field note : How to Inspect JSON With an Anti-XSSI PrefixRead GeoJSON positions as longitude first and latitude second. Check syntax, structure and geographic plausibility separately, then use documented location evidence to resolve ambiguity…
Read field note : Check Longitude and Latitude Order in GeoJSONAn unquoted < cannot begin a valid JSON value. Inspect what the endpoint returned, distinguish syntax errors from HTTP outcomes, and use local examples…
Read field note : Why an API Response Starting With < Fails JSON ParsingA field containing the word false may contain a string instead of a boolean. Compare its notation, inspect the exact field in your application,…
Read field note : How to Spot a Boolean Sent as a String in JSON