Write Page Titles and Meta Descriptions That Match the Page
A page-by-page method for writing accurate search snippets, checking title length in context, and avoiding repetitive or misleading metadata.
Encode or decode URLs and query parameters instantly
Encode or decode URLs and query parameters instantly
Use the URL Encoder/Decoder when you need the specific operation described above. Choose the input and options that match your intended output, then check the result before using it elsewhere.
Paste the text, token, URL, regex, or hash input the tool expects.
The browser will parse, validate, decode, or transform the content instantly on your device.
Review the structured output, highlighted matches, or decoded fields returned by the tool.
Copy the result into your app, debugging workflow, or documentation pipeline.
Developer utilities interpret input according to browser APIs and web standards. A decoded value is not automatically trusted: validate its structure and do not treat parsing or decoding as cryptographic verification.
Developer utilities interpret input according to browser APIs and web standards. A decoded value is not automatically trusted: validate its structure and do not treat parsing or decoding as cryptographic verification.
Treat input as untrusted and verify the result in the target runtime. Decoding, formatting, and hashing are not substitutes for authorization or secure key management.
The tool is a focused utility rather than a substitute for reviewing the final file or data in its destination. Keep an unchanged source when the input is important, and use the relevant specialist software for requirements the page does not claim to support.
URL encoding replaces unsafe characters with a % followed by two hex digits, making the string safe to use in a URL.
Use encodeURIComponent for individual query values (it encodes more characters). Use encodeURI for full URLs.
In query strings a space may be sent as +, while percent-encoding sends %20. The tool lets you pick the convention your server expects.
No. Encoding and decoding use the browser's built-in escape functions locally, so internal or signed URLs stay on your device.
Percent-sequences must form valid UTF-8 byte pairs. If the input is truncated or double-encoded, decoding fails — check for a missing % or an already-encoded string.
Nothing is transmitted, because every tool runs locally in your browser. Even so, treat live secrets with care and prefer test fixtures over production credentials.
Popular practical guides
A page-by-page method for writing accurate search snippets, checking title length in context, and avoiding repetitive or misleading metadata.
Learn when to change pixel dimensions, when to compress, how to preserve aspect ratio, and how to inspect an exported image before publishing.
A practical checklist for combining PDFs: prepare the source files, set their order, verify page boundaries, and keep the originals unchanged.