Encode & Hash
URL Encode
Paste text on the left, hit Run, copy bytes represented safely for URLs, HTML, or transport. No Node, no pip, no Docker for a five-minute job. That is the url encode.
Drop a file on the left. Drafts stay in this browser. Shortcut: Ctrl or Cmd + Enter to run.
How this url encode works
- Paste or drop a .txt file into the input on the left.
- Flip options if you see them (comments, indent, case). Defaults are the safe ones.
- Hit Run, or Ctrl / Cmd + Enter. Leave “Process on server” off unless you mean it.
- Read the status line, then copy, download, or jump to a related tool.
What this url encode is for
The file is already in front of you. You need to encode it without opening a whole IDE profile. Paste, run, copy. Typical timing: you need Base64, percent-encoding, entities, or a checksum — plumbing, not poetry.
You walk away with bytes represented safely for URLs, HTML, or transport.
What it will not pretend to be
This is not encryption. Hashes are one-way; Base64 is not a secret. Treat this as a text transform. Encoding, hashing, and diffs do not “understand” your programming language.
By default nothing leaves the tab. Tick “Process on server” only if you want to compare results or use gzip numbers that match the server library.
A practical way to use it
Drop a .txt file onto the input or paste. Flip options if they are there. Run. Read the status line. Copy or download. Drafts stay on this device so a refresh does not punish you.
When you are done, hop a related tool instead of starting over: minify and beautify toss the file back and forth, format and validate often share a parser, convert wants valid input first.
The small print that saves a round-trip
Treat this as a text transform. Encoding, hashing, and diffs do not “understand” your programming language.
You searched “url encode online.” You got an editor, not a login wall. That is the deal.
Frequently asked questions
What does URL encode change?
Characters that are not safe in a query component become %HH. Space becomes %20 (or + in some query styles). hello world → hello%20world. / and ? in a parameter should be encoded so they are not “more URL.”
encodeURI vs encodeURIComponent?
encodeURI leaves URL structure (:/?#) alone. encodeURIComponent encodes those too — correct for a single parameter value. Encoding a whole URL with the component function will smash https://. Encode the parts.
Example of a trap?
A search query tea & crumpets. Unencoded & starts a new query parameter. Encoded: tea%20%26%20crumpets. Your analytics stop growing a fake crumpets key.
Fun fact?
Fun fact: %20 and + can both mean space in query strings, depending on the form encoding (application/x-www-form-urlencoded). Path segments prefer %20. If a decoder “eats” plus signs, you found that fork.
Should I encode Unicode?
Yes — as UTF-8 bytes, then percent-encode. café becomes caf%C3%A9. Older ISO-8859-1 encodings still haunt old PHP apps. If one browser shows café, that is a UTF-8 string read as Latin-1.
Double encoding?
% encoded twice becomes %2520 for a space. APIs that encode “just in case” cause that. Decode until it looks like text, not until it looks like soup.
Path vs query vs fragment?
Each has slightly different allowed characters. Fragments (#section) never hit the server. Query values are the usual encode job. Do not encode the # if you still want a fragment.
URL encode vs HTML encode?
HTML encode turns < into < for markup. URL encode turns < into %3C for URLs. Using the wrong one is a classic XSS-or-404 cocktail.