Key takeaway
URL encoding (percent-encoding) replaces reserved or unsafe characters with %HH so URLs remain valid. Spaces often become %20 (or + in some query contexts).
Unencoded query values break parsers and analytics.
What it means
Reserved characters like &, =, ?, # change URL meaning if raw.
UTF-8 bytes are percent-encoded for non-ASCII.
Encoding is not encryption.
When you would use it
Building query strings, OAuth redirects, search params, UTM values with odd characters.
How to use the tool
Use the matching TCB Tools page and work top to bottom:
- Open URL Encoder/Decoder.
- Paste the component or full string carefully.
- Encode values (usually not the whole URL blindly).
- Decode to inspect.
No account is required. Results update as you type.
How encoding works + example
Example: hello world → hello%20world.
Example: a&b=c must encode & and = inside values.
Do not encode the structure characters you mean to keep as syntax.
How to read the result
Encode values; keep scheme/host/path structure intentional.
Double-encoding creates %25 artifacts.
Dev aid.
Common mistakes
- Encoding the entire URL including https://. Encode components.
- Double encoding. Once.
- Forgetting UTF-8. Use proper bytes.
- Assuming + always means space. Context matters.
Related ideas
Build campaigns with the UTM Builder; pair with JSON tools when APIs mix formats.
Log raw and encoded forms during debugging.
Test redirects in a clean browser profile.
If you are new, read once for the story, then again for the clicks you will make.
Write inputs down before changing live budgets or deleting files — calm beats guesswork.
Note the date range, currency or filename so teammates can reproduce the result.
Interactive math and many file jobs run in your browser here; treat outputs as planning aids, not certified professional advice.
When a result looks too good, recheck definitions: units, filters and windows hide surprises.
Practice with example numbers first, then replace them with trusted exports.
Small disagreements between systems are often rounding or filters — investigate before panicking.
Consistent naming, windows and currencies beat clever one-off spreadsheets.
Operators who revisit URL encoding weekly catch drift earlier than teams who only look after emergencies.
Teach one teammate how you measure URL encoding; shared definitions prevent quiet disagreement.
Bookmark the guide and the tool together so beginners always have both the why and the workspace.
When unsure about URL encoding, reduce scope: one campaign, one file, one list — prove the method, then scale.
Screenshots of inputs beside outputs speed audits when someone questions URL encoding.
If leadership wants only a headline, still keep working notes for URL encoding in your own folder.
Seasonality and promotions change URL encoding; annotate the calendar when comparing periods.
Automation helps, but a human still owns success criteria for URL encoding.
Revisit assumptions about URL encoding after tool, tracking or pricing changes.
A short checklist for URL encoding beats relying on memory during busy weeks.
Log raw and encoded forms during debugging.
Test redirects in a clean browser profile.
If you are new, read once for the story, then again for the clicks you will make.
Write inputs down before changing live budgets or deleting files — calm beats guesswork.
Note the date range, currency or filename so teammates can reproduce the result.
Interactive math and many file jobs run in your browser here; treat outputs as planning aids, not certified professional advice.
When a result looks too good, recheck definitions: units, filters and windows hide surprises.
Practice with example numbers first, then replace them with trusted exports.
Small disagreements between systems are often rounding or filters — investigate before panicking.
Consistent naming, windows and currencies beat clever one-off spreadsheets.
Operators who revisit URL encoding weekly catch drift earlier than teams who only look after emergencies.
Teach one teammate how you measure URL encoding; shared definitions prevent quiet disagreement.
Bookmark the guide and the tool together so beginners always have both the why and the workspace.
When unsure about URL encoding, reduce scope: one campaign, one file, one list — prove the method, then scale.
Screenshots of inputs beside outputs speed audits when someone questions URL encoding.
If leadership wants only a headline, still keep working notes for URL encoding in your own folder.
Seasonality and promotions change URL encoding; annotate the calendar when comparing periods.
Automation helps, but a human still owns success criteria for URL encoding.
Revisit assumptions about URL encoding after tool, tracking or pricing changes.
A short checklist for URL encoding beats relying on memory during busy weeks.
Log raw and encoded forms during debugging.
Test redirects in a clean browser profile.
If you are new, read once for the story, then again for the clicks you will make.
Write inputs down before changing live budgets or deleting files — calm beats guesswork.
Note the date range, currency or filename so teammates can reproduce the result.
Interactive math and many file jobs run in your browser here; treat outputs as planning aids, not certified professional advice.
When a result looks too good, recheck definitions: units, filters and windows hide surprises.
Practice with example numbers first, then replace them with trusted exports.
Small disagreements between systems are often rounding or filters — investigate before panicking.
Consistent naming, windows and currencies beat clever one-off spreadsheets.
Operators who revisit URL encoding weekly catch drift earlier than teams who only look after emergencies.
Teach one teammate how you measure URL encoding; shared definitions prevent quiet disagreement.
Bookmark the guide and the tool together so beginners always have both the why and the workspace.
When unsure about URL encoding, reduce scope: one campaign, one file, one list — prove the method, then scale.
Screenshots of inputs beside outputs speed audits when someone questions URL encoding.
If leadership wants only a headline, still keep working notes for URL encoding in your own folder.
Seasonality and promotions change URL encoding; annotate the calendar when comparing periods.
Automation helps, but a human still owns success criteria for URL encoding.
Revisit assumptions about URL encoding after tool, tracking or pricing changes.
A short checklist for URL encoding beats relying on memory during busy weeks.
Log raw and encoded forms during debugging.
Test redirects in a clean browser profile.
If you are new, read once for the story, then again for the clicks you will make.
Try the tools
Try the URL Encoder & Decoder.
