Developer tools include JSON viewing, Base64 and binary conversion, URL encoding, JWT decoding, regular-expression testing, QR utilities, password generation and colour conversion.

When to use them

Use these tools for debugging API responses, preparing encoded values, checking patterns, inspecting tokens and creating small development assets.

Frequently asked questions

Does the JWT decoder verify signatures?

No. Decoding makes the header and payload readable but does not prove that the token is authentic.

Can JSON be valid but still wrong?

Yes. Syntax validation confirms that the JSON can be parsed; an API may still reject valid JSON when fields or value types do not match its expected schema.

Are generated passwords saved?

The Password Generator creates values in the browser. Copy them into a trusted password manager rather than storing them in an unsecured note.

What this category covers

Developer tools format, validate, encode and inspect code or structured data. They are intended for reproducible debugging tasks such as finding malformed JSON, testing a regular expression or decoding a URL component.

Recommended starting tools

JSON Viewer — Format, validate and inspect JSON data in a readable structured view.
Regex Tester — Test regular expressions, inspect matches and preview replacements against pasted text.
URL Encoder/Decoder — Encode or decode URL components containing spaces, symbols and Unicode text.

How to choose

Choose a validator before a formatter when syntax may be broken. Keep a minimal failing example and never paste production secrets into a diagnostic field.

Frequently asked questions

Can a formatter fix invalid data?

A formatter can reorganise valid input, but malformed syntax normally needs a specific correction first.

Which regex flavour is used?

The Regex Tester uses the JavaScript regular-expression engine exposed by the current browser.