Developer tools

Small utilities that save time during coding and testing.

Tools in this category

Developer tools

JSON Formatter & Validator

Pretty-print, minify, and validate JSON directly in your browser.

Runs in your browserOpen tool →
Developer tools

Base64 Encoder & Decoder

Convert text to Base64 and back, entirely in your browser.

Runs in your browserOpen tool →
Developer tools

User-Agent String Reference

Reference strings for parser and request-header tests in applications you own or are authorized to test.

Runs in your browserOpen tool →
Developer tools

URL Encoder & Decoder

Encode text for a URL or decode percent-encoded values safely.

Runs in your browserOpen tool →
Developer tools

JWT Decoder

Inspect a JWT header and payload without uploading the token.

Runs in your browserOpen tool →
Developer tools

Unix Timestamp Converter

Convert Unix seconds or milliseconds to readable local and UTC dates.

Runs in your browserOpen tool →
Developer tools

Hash Generator

Generate SHA-256, SHA-384, or SHA-512 hashes from UTF-8 text.

Runs in your browserOpen tool →
Developer tools

CSV to JSON Converter

Convert quoted CSV data into JSON arrays or objects locally.

Runs in your browserOpen tool →

Find the transformation boundary

ProblemToolBoundary to preserve
A configuration fails to parseJSON FormatterValid syntax, intended types, duplicate keys, and large identifiers.
A spreadsheet export needs API fixturesCSV to JSONQuoted commas, consistent columns, and string identifiers such as 001.
A query value contains spaces or reserved charactersURL Encoder/DecoderOne component versus the separators of a complete URL.
A text payload uses an encoded representationBase64 Encoder/DecoderUTF-8 text, standard Base64 versus Base64url, and unchanged bytes.
A test token's claims need inspectionJWT DecoderDecoded claims remain unverified; never use a live login token as a public example.
A timestamp or digest differsTimestamp Converter or Hash GeneratorSeconds versus milliseconds and timezone, or exact UTF-8 text and line endings.
A client parser needs sample inputUser-Agent String ReferenceFixed fixtures versus real browser behavior and authenticated identities.

Debug one fictional record

Convert id,name followed by 001,Amina from CSV to JSON. With headers enabled, the result contains {"id":"001","name":"Amina"}; the leading-zero identifier stays a string. Format it to inspect the types, then encode only the intended query value if it needs to enter a URL. If a later digest differs, compare the exact text and line endings before suspecting the algorithm.

The developer debugging guide works through connected examples and shows why decoding, formatting, hashing, and server-side validation solve different problems.

Reproduce a transformation boundary

id,id followed by 001,002 produces Header names must be unique. A quoted newline belongs to one field. Download the CSV and compare the expected JSON.

Compare recorded parser results

The JSON experiment records malformed inputs, duplicate keys, and a large integer that changes. The CSV experiment records quoted newlines, BOM handling, duplicate headers, and a delimiter mismatch. Use these fixtures with the developer workflow guide; formatting or decoding does not validate authorization or business rules.

For a fictional record identifier, UUID Generator creates random version 4 values. Enforce uniqueness and access checks in the receiving application; possession of an identifier does not grant permission.

All developer tools guides

Reviewed guides, related tools, and the latest recorded review date.