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.
Choose encodeURI for an already structured URL whose syntax should remain meaningful, and encodeURIComponent for individual data components. Learn how to preserve boundaries, inspect…
Read field note : encodeURI vs. encodeURIComponent: Choose the Right BoundaryWhen copied JSON contains ", first determine whether it occupies required quotation-mark positions or belongs inside a valid string. Preserve the input, compare it…
Read field note : JSON Copied From HTML: Checking " and Intended ValuesChanging indentation and line breaks preserves an array’s sequence, length, and repeated elements. Use a positional comparison and a runnable example to distinguish formatting…
Read field note : Does Formatting JSON Change Array Element Order?Double quotes are part of JSON's grammar. Learn how to correct JavaScript-style object text, preserve apostrophes and quotation marks, serialize an existing object, and…
Read field note : Why JSON Requires Double Quotes Around Strings and Property NamesCompare an API's schema error with the exact transmitted body and the correct request contract. Follow a fictional schema through missing fields, incorrect types,…
Read field note : Why Valid JSON Can Fail an API Schema CheckInspect percent-encoded URLs by preserving the original input, selecting the appropriate component, and recording byte conversion separately from text interpretation. Follow a practical workflow…
Read field note : Inspect Percent-Encoded UTF-8 URLs and Trace Conversion Stages