Converter Tools
Encode and decode Base64, escape URLs, switch between data formats, all in your browser. Files dropped on these pages are read locally via FileReader and never leave your tab.
Encoders for everyday formats
Two converters live today: Base64 (text and files) and URL Encoder (query-string + path). Format, base and encoding matrices are on the roadmap below.
Start with Base64 if you have a file or string to encode, or URL Encoder for query-string work.
Frequently Asked Questions
What's the difference between Base64 and URL encoding?
Base64 encodes binary data as ASCII (using 64 characters), often to carry data in a text-only context like an email or a JSON payload. URL encoding (percent-encoding) escapes reserved characters inside a URL so they're not interpreted as separators. Different problems, different tools.
Can I convert binary files (images, PDFs) to Base64?
Yes, the Base64 encoder accepts files via drag and drop. The file is read with FileReader in your browser; nothing is uploaded.
Why no JSON ↔ YAML / TOML / XML / CSV conversions yet?
Planned. We're building 20 dedicated /<format-a>-to-<format-b>/ pages (JSON ↔ YAML, JSON ↔ TOML, CSV ↔ JSON, etc.) so each conversion ranks on its own keyword. See tool-longtail-format-matrix on our roadmap.
Are there size limits on conversions?
Limited by browser RAM, not by us. A 50 MB file converted to Base64 stays manageable on a modern machine; beyond that, latency becomes noticeable. No request leaves your tab regardless of size.
Can I batch-convert multiple inputs at once?
Not in the current UI. For high-volume or scripted workflows, the planned public API (api.praticulus.com/v1) will be the right fit. Until then, each tool handles one payload at a time.