Guide
URL, HTML, JSON, and CSV: which encoder or converter to use
Separates URL encoding, HTML escaping, JSON formatting/validation, and JSON↔CSV interchange so you reach the right developer or converter page.
URL encoding: safe characters inside addresses
Use the URL encoder when you need query parameters, path segments, or fragments to survive transport inside URLs and forms.
Do not confuse encoding with authorization: encoding does not stop someone who already has the link from reading it.
HTML escaping: safe text inside markup
Use HTML escape when you are embedding dynamic text inside tags or attributes and need to avoid breaking structure or injecting unintended markup.
Escaping is contextual: what is safe inside text nodes may still be unsafe inside an attribute without quotes.
JSON: structure, formatting, and validation
Use the JSON formatter when you need readability or minification for debugging and handoffs.
Use the JSON Schema validator when you need machine-checkable constraints beyond “it parses.”
JSON ↔ CSV: tabular interchange
Use the JSON/CSV converter when you are moving between spreadsheet-friendly rows and structured arrays for APIs or configs.
Watch for delimiter ambiguity, quoting, and numeric locale issues when round-tripping.
Pick a tool
FAQ
Should I URL-encode before Base64?
They solve different problems. Encode URLs for address safety; Base64 for binary-to-text representation—not interchangeable steps.
Does JSON formatting protect secrets?
No. It only changes presentation. Treat JSON like any other sensitive text.
When do I need JSON Schema instead of formatter?
When you must assert required fields, types, ranges, or enums—not just pretty-print.
Can I skip HTML escaping if I trust the input?
Trust boundaries move. Escaping is cheap insurance against future template changes and accidental double interpolation.
CSV broke after conversion—why?
Common causes include embedded commas/newlines, inconsistent quoting, and locale-specific number formats.