Web & URLs

URL encode / decode

Percent-encode text for query strings or decode encoded values back to plain text.

URLs only allow a limited character set in query components. `encodeURIComponent` style encoding keeps spaces, slashes, and Unicode safely escaped for use inside `?key=value` pairs. Decoding reverses that process when you are inspecting a copied URL or debugging redirects.

Similar tools

Quick links to related utilities—same workflow, different input or output.

FAQs

encodeURIComponent vs encodeURI?

This tool follows component encoding: safe for individual parameter values. `encodeURI` is looser and meant for whole URIs.

Why do I see %20 or + for spaces?

Both appear in the wild; decoders usually accept them. This tool follows standard decode behavior for pasted strings.

Can I encode a full URL?

Encode individual components (path segments or query values) rather than blindly encoding `https://…` or you may break the scheme and host.

Is decoding lossless?

For UTF-8 text, yes. Binary payloads may need different handling than plain strings.

General

Do these tools send my data to Exemplar’s servers?

By default, conversion and formatting run entirely in your browser. Nothing is uploaded to Exemplar for normal paste-and-transform workflows. Tools that deliberately open an external service (for example, a third-party speed test) are called out on the page.

Do I need an account or install anything?

No account is required. Everything runs in the browser—there is nothing to install for these utilities. They complement the Exemplar platform but work standalone.

Are these utilities open-source or the same as other sites?

These pages are built for Exemplar’s audience (developers working with APIs, config, and ops data). Behavior may differ slightly from other online tools; always verify critical output in your own environment.

Are there size or performance limits?

Very large inputs can slow down or crash the tab—especially for images, huge JSON, or multi‑MB HAR files. For production-scale data, prefer local CLI tools, streaming parsers, or your own pipelines.

Can I use output in production?

Yes, when you have validated it. Parsers and formatters here aim to be helpful for everyday tasks but are not a substitute for tests, schema validation, or security review where it matters.

Where can I read more about privacy?

See our Privacy policy at /privacy for how exemplar.dev handles site analytics and general data practices.