Free Online Developer Tools for Formatting, Encoding and Debugging
Small jobs that interrupt real work: pretty-print a minified API response, find the trailing comma that breaks a config file, read the claims inside a token from a failing login, see when a cron line will really fire, or convert CSS units. Developers, sysadmins and QA engineers can paste real payloads here, because almost every tool processes them locally in the browser.
Formatters, encoders, hashing, JWT decoding, regex, cron and converter tools process what you paste on your own device. Nothing you paste into them is uploaded to our servers.
🌐
Two tools make network requests
The HTTP Status Checker sends the URL you enter to our server, which fetches it. The API Tester sends your request from your browser straight to the API you name.
🎯
Errors that point to the spot
The JSON, JavaScript, CSS, XML and YAML tools report the line and column of the first syntax error, and the JSON tools add a plain-English hint for common mistakes.
📐
Built on real standards
Contrast follows the WCAG formula, JSON checking follows RFC 8259, SHA hashes use your browser's Web Crypto API and UUIDs come from its secure random generator.
Most popular developer tools
The tools most visitors start with, and what each one is for.
Why JSON that looks fine still fails to parse: trailing commas, single quotes, comments, NaN and oversized numbers, and how to validate, format and compare it fast.
Base64 is not encryption and a hash cannot be reversed. See what each does, where JWTs and URL encoding fit, and how to pick MD5, SHA-256 or a password hash.
Each group explains what its tools are for, so you can find the right one without scrolling a long list.
Formatters and beautifiers (7)
Turn minified or messy code into readable, consistently indented text. JavaScript, CSS, HTML, JSON, SQL, XML and YAML are covered, and each formatter reports syntax errors instead of quietly guessing.
Check that something is correct before it ships: strict JSON syntax, the differences between two JSON documents, a regular expression against sample text, and a cron schedule against its upcoming run times.
Encode and decode Base64, Base32 and percent-escaped text, compute MD5 and SHA checksums and HMACs, read the claims inside a JWT, and generate random version 4 UUIDs. All of it runs in your browser.
Move content between formats: Markdown and HTML in both directions with a live preview, XML to JSON, CSS into inline style attributes for HTML email, and a regular expression into a string for JSON or another language.
Inspect the pieces of a web request: split a URL into parts and query parameters, identify a browser from its user agent string, read pasted response headers for security gaps, check a live status code, or send a test API call.
Work out sizes and readability for the front end: convert px, rem, em and vw values, check text and background colors against WCAG contrast thresholds, and make placeholder images for mockups.
Formatters, decoders, hashing and converters run locally, so you can paste real payloads and config files without uploading them. Only two tools make network requests: the HTTP Status Checker and the API Tester.
Errors that tell you where to look
The JSON, JavaScript, CSS, XML and YAML tools report the line and column of the first syntax error, and the JSON tools explain trailing commas, single quotes, comments and unquoted keys.
The whole debugging loop in one place
Format a response, validate it, diff it against the previous version, decode the token that came with it, then test the regex or cron rule that handles it, all without switching sites.
No install, account or extension
Open a tool, paste, copy the result. That works on a locked-down work laptop, a colleague's machine or a phone during an incident, where installing a formatter or a plugin is not an option.
Limits are stated, not hidden
The JWT decoder does not verify signatures, the regex tester uses the JavaScript flavor, the cron parser follows Vixie rules, and the hash generator notes that MD5 and SHA-1 are not safe for security use.
How these tools are built and checked
Each tool uses an established library or standard where correctness matters. JavaScript, TypeScript, CSS, SCSS, Less, HTML, YAML and Markdown formatting use Prettier; SQL formatting uses the sql-formatter library; Markdown conversion uses marked and Turndown, and the Markdown preview is sanitized with DOMPurify. JSON checking uses a strict RFC 8259 scanner written to give exact line and column positions. Hashes come from the Web Crypto API, plus a separate MD5 implementation because Web Crypto leaves MD5 out, and cron parsing uses the cron-parser and cronstrue libraries. Where a tool has known limits, such as unverified JWT signatures or Vixie-only cron syntax, its page says so.
The JWT Decoder here decodes in your browser and the token is not sent anywhere, but safety also depends on the token. A live token is a credential: anyone who holds it can use it until it expires. Prefer expired or test tokens, rotate a token you pasted into a site you do not control, and remember that the decoder checks structure and claims but does not verify the signature.
Does Base64 hide or protect my data?
No. Base64 is an encoding that turns bytes into 64 printable characters. Anyone can reverse it, and it makes data about a third larger. It exists to carry binary data through text-only channels such as JSON, email and data URLs. To keep something secret you need encryption, and to store a password you need a slow, salted hash. Base64 provides neither.
Why does my JSON fail to parse when it looks correct?
Strict JSON rejects several things that JavaScript accepts: trailing commas, single quotes, unquoted keys, comments, NaN and Infinity values, leading zeros in numbers and raw line breaks inside strings. An invisible byte order mark at the start of a file fails too. The JSON Validator shows the line and column of the first error and explains the usual causes.
Which hash should I use to verify a downloaded file?
Use SHA-256 or SHA-512 and compare the result with the checksum the publisher lists. MD5 and SHA-1 still catch accidental corruption but are broken against deliberate tampering. The Hash Generator reads files up to 200 MB in your browser. Plain hashes are not a way to store passwords, which need a salted, deliberately slow algorithm such as bcrypt or Argon2.
Can the Regex Tester run PCRE, Python or Java patterns?
It uses your browser's JavaScript regular expression engine, so patterns written for other flavors may behave differently or fail. Possessive quantifiers and atomic groups, for example, do not exist in JavaScript. Test JavaScript patterns directly, and use Regex to String to get a pattern as a JSON string, a JavaScript constructor call or a Python raw string.
Does the Cron Parser understand Quartz or Spring expressions?
It follows common Vixie cron rules: five fields, an optional leading seconds field, names such as MON and JAN, and shortcuts like @daily. Quartz extras such as L, W and # are not supported. It lists upcoming runs in the time zone you pick, which helps because cron normally uses the server's time zone, often UTC.
Which developer tools send data to a server?
Two. The HTTP Status Checker sends the URL you enter to our server, which requests it and reports status, redirects, timing and SSL details; it only checks public addresses and is rate limited. The API Tester sends requests from your browser directly to the API you enter, so that API must allow cross-origin requests (CORS) for the call to succeed. Every other tool stays in the page.