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.
Read structured API errors by combining response metadata, the JSON body, and the API contract. Follow an invented validation response, distinguish problem-details members from…
Read field note : How to Interpret application/problem+json API ErrorsIn JSON Pointer tokens, ~1 represents a slash and ~0 represents a tilde. Learn how to decode an API error location, trace it through…
Read field note : What ~0 and ~1 Mean in JSON Pointer PathsEscaping a forward slash changes the JSON text while preserving the decoded slash character. Compare source text and parsed values separately, recognize when a…
Read field note : Does Escaping a Forward Slash Change a JSON String?Restore copied JSON in separate stages: establish what was copied, extract the intended CSV field when needed, validate its JSON syntax and format it…
Read field note : How to Restore JSON Copied From a CSV FieldStart by identifying what your client has given you. Keep response metadata outside the JSON input, establish whether decoding work remains, and distinguish body-reading…
Read field note : How to Extract and Format JSON From an HTTP Response With HeadersChoose 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 Boundary