Tools that speed up
your dev work

The developer category has five groups: Convert & Encode for turning a value into another form, Generate & Verify for creating new values or checking their integrity, Utilities for other operations and debugging tasks, Web, CSS & Color for front-end work, and Code Generators for QR/barcode images.

If you're not sure where to look, ask whether you're "reshaping an existing value" (Convert & Encode) or "creating a new value, or checking one" (Generate & Verify) — that usually narrows it down fast.

All twenty-two tools run purely in client-side JavaScript with no backend, so pasting a sensitive value like an API key or token to parse it never stores or transmits that value anywhere.

Routine development checks are mostly conversion and validation. Pretty-printing JSON and locating a syntax error, switching encodings, comparing hash values — each is faster through a tool than by writing code every time.

JSON is readable but breaks on a single comma. Trailing commas, single-quoted strings and comments are not valid, so object notation copied from another language fails to parse.

Encoding is not encryption. Base64 merely maps binary data to characters and needs no key to reverse, so wrapping a password or token in it offers no protection — exposed, it reads straight through.

A hash is a one-way function used to verify that a file is unchanged or to store passwords. Because identical input always yields the same value, common passwords fall to precomputed tables, which is why password storage uses a random salt and a purpose-built algorithm with deliberate repetition.

A JWT is signed, not encrypted. The payload is only Base64-encoded and anyone can read it; the signature guarantees only that the contents were not altered, so sensitive data placed in the payload is exposed.

Regular expressions are powerful and hard to read. Supported syntax differs between languages and engines, so a pattern working in one place can error or match differently in another — complex expressions are safer kept with comments and checked against real input.

Timestamps need their epoch and unit confirmed. Seconds and milliseconds are both in use and values often lack zone information, so misreading the same number can be off by days or decades. Storing in UTC and applying a local zone at display time avoids most of this.

HTTP status codes signal the nature of a response: the 400 range points at the request and the 500 range at the server. Blurring that distinction sends debugging to the wrong place, and among redirects the permanent-versus-temporary split changes both search indexing and caching.

Colour contrast has numeric accessibility thresholds. Body text failing the ratio against its background is hard for low-vision users to read, and checking during design avoids reworking a whole palette later.

A cron expression assigns meaning by position, so a misplaced field changes the schedule substantially. Behaviour when both day-of-month and day-of-week are set varies between implementations, making it worth confirming the next run time before deploying.

These tools process input inside the browser. Values containing tokens or keys are not transmitted, though anything left on screen has to be cleared manually.