Most “it is just text” bugs are actually format wars. A CI job rejects YAML because someone pasted tabs. A CSV import explodes because a vendor wrapped addresses in quotes but not consistently. A JSON payload is valid JavaScript but not valid JSON. A block of HTML is readable until it ships minified and reviewers stop reading it. The fix is rarely “try harder.” The fix is a repeatable pipeline: validate structure, normalize whitespace for the audience, then move data between systems with explicit contracts.
Five sibling jobs people confuse on purpose
JSON minify cares about bytes on the wire. JSON pretty-print cares about human diffs. JSON validate cares whether JSON.parse can succeed at all. YAML validate cares whether your Helm values file can even load. CSV to JSON cares whether the first spreadsheet row can become stable keys for a mock API. None of those jobs replace each other, but they all show up in the same incident channel when a deploy fails at 6pm.
Toollabz keeps each job in a focused calculator so you can paste, click, and move on. Start with the JSON minifier when you need a single-line body for a signed request example. Reach for the JSON formatter when you are reviewing nested config with a teammate. Use the JSON validator when the error message is simply “unexpected token” and you want a fast yes/no before blaming upstream.
YAML: indentation is semantics, not style
YAML rewards authors with readable blocks, then punishes them with two-space mistakes that move a key under the wrong parent. A parse error at line 84 might be caused by line 19 where someone duplicated a key. That is why a syntax validator belongs near the editor, not only in CI. The YAML validator answers the narrow question: does this file parse as YAML right now? It does not replace kubeconform, policy tests, or a human review of secrets. It does stop the “I swear this file is fine” argument when two laptops disagree because one editor auto-converted tabs.
Practical workflow: validate locally, commit, let CI run schema checks, then promote. If you skip local validation, you pay the cost in queue time and context switches. If you only validate locally and never in CI, you get drift when someone edits on the web UI. Pair YAML checks with the JSON formatting and validation guide when the same repo mixes JSON and YAML configs, which is common in GitHub Actions plus Helm stacks.
CSV to JSON: contracts for prototypes, not religions
Product and ops teams think in spreadsheets. Engineering thinks in objects. The translation layer is where commas inside addresses ruin afternoons. The CSV to JSON converter assumes a header row and preserves quoted fields so you can paste a small sample and generate a JSON array for Postman, OpenAPI examples, or a seed fixture. If you need strict typing, cast in application code. If you need huge files, chunk in a script. The browser tool is for clarity and speed on human-sized samples.
When vendors ship semicolon-separated CSV, normalize delimiters first. When finance exports include merged cells, flatten before export. When marketing exports include a UTF-8 BOM, strip it so your header row does not become \ufeffname. Those are boring details until they are not.
HTML formatter: readability without pretending to be a browser
Email templates, CMS exports, and legacy admin panels often arrive as one long line. Reviewers either rubber-stamp or burn out. The HTML formatter inserts line breaks between tags so you can scan structure before you sanitize and ship. It is not a validator and it is not a security boundary. XSS questions still belong to your platform policy and your CSP headers.
If you also ship CSS bundles, pair HTML cleanup with the CSS minifier when you want a smaller handoff artifact for edge demos. Keep the authored stylesheet in git with comments; minify copies for deployment previews.
API “status” from a laptop: honesty beats theater
Browsers lie kindly about cross-origin health checks. Terminals lie less. The API URL checker validates URL structure and prints a curl probe you can paste into a shell. It does not perform async network calls inside the synchronous calculator engine, because that would break predictable tests and still would not prove TLS trust paths on every machine. Use curl or your observability stack for authoritative status codes, then return here when you need a quick sanity check on malformed URLs before sharing a runbook link.
Comparison: which tool answers which panic sentence
| Panic sentence | Reach for |
|---|---|
| “Terraform says JSON invalid.” | JSON validator, then formatter |
| “Helm upgrade says YAML error line 40.” | YAML validator |
| “Postman body must be one line.” | JSON minifier |
| “PM sent a CSV, I need JSON examples.” | CSV to JSON converter |
| “This HTML is unreadable in the ticket.” | HTML formatter |
Common mistakes that survive code review
- Treating JSON5, HOCON, or relaxed supersets as strict JSON in production parsers.
- Pasting production secrets into any online textarea, even when processing is local.
- Letting CSV Excel exports silently change number cells into localized decimals.
- Assuming “validated YAML” means “safe to apply to prod.”
- Minifying without keeping a readable source artifact for auditors.
When to use this cluster on Toollabz
- During incident bridges when you need fast structure checks without opening five desktop apps.
- When onboarding interns who need guardrails before touching shared repos.
- When writing internal runbooks that should include copy-pasteable curl and JSON samples.
- When product and engineering want a shared artifact for mock API rows.
Cluster links: regex, SQL, cron, JWT
Text pipelines rarely live alone. Pair this cluster with the regex beginner guide, the SQL and cron readability walkthrough, and the JWT decode vs verify security guide when logs, schedules, and auth traces show up in the same ticket.
Browse the full developer tools hub for adjacent utilities like URL encoding and Base64 helpers.