Skip to main content
CaseSwitch

Code and data tools

Developer utilities for JSON, encoding, naming conventions, code formatters, regex, QR codes, and UTM links. Format and convert structured text in your browser without uploading payloads.

Focused developer hubs

Open a topical cluster when you already know the task — JSON, encoding, naming, or formatters — instead of scrolling the full Code & Data list.

Developer naming

camelCase, PascalCase, snake_case, kebab-case, and URL slugs. Pick one layer and stay there.

JSON and data formats

Pretty-print, minify, stringify, and convert JSON, YAML, CSV, and XML in the tab.

Encoding and hashes

Base64, URL encoding, and checksums. MD5 is a fingerprint, not a password store.

More in this category

About this category

Treat this category as CaseSwitch’s second pillar after case conversion. Focused hubs make discovery clearer: JSON Tools, Code Formatters, Encoding Tools, Naming Convention Tools, and the broader Developer Tools hub — each links related converters without repeating the full catalog.

Use kebab-case and the slug generator for public URLs. Use camelCase and PascalCase for JavaScript and React. Use snake_case for Python and SQL. Mixing those layers without a mapping strategy is how APIs drift. Convert the name here, then rename call sites in your IDE.

JSON formatters pretty-print and minify with strict parse errors. Encoding tools cover Base64 and URL encoding with clear “not encryption” guidance. Formatters indent HTML, CSS, JS, and TypeScript snippets for review — then let CI Prettier own the repo style.

MD5, Caesar, and ROT13 are documented with their real strength (checksum or toy), not as security products. Regex testing is JS-dialect and can lock a tab if you explode backtracking on a huge paste. Start with a small sample when debugging.

Frequently asked questions

Where do I find JSON-only tools?+

Open the JSON Tools hub for formatter, stringify, unstringify, JSON to YAML, and CSV to JSON in one place.

Does the JSON formatter also validate?+

Yes as a parse check. Invalid JSON returns an error instead of a silently broken file. Trailing commas and comments are not valid in standard JSON.

Which naming style should I use for URLs?+

Use kebab-case or the Slug Generator for public paths. camelCase and PascalCase belong in JavaScript identifiers, not in paths people type.

Are API payloads uploaded?+

No. Formatting and encoding run in this browser. Still avoid pasting production secrets into screenshots.

Related guides