Bulk URL Encoder - Percent-Encode Multiple URLs
Percent-encode up to 100,000 URLs and query strings at once while keeping 1:1 row order.
If your URLs are combined on one line, divide them into rows first with our Text Splitter.
🔒 Data Safety: We process everything securely and never store or share it.
How to Use
- Paste your URLs or query strings into the box above (one per line), or click "Sample".
- Check the options below the input box for + spaces, strict RFC 3986, or URL structure preservation.
- Click "Encode" to percent-encode every row in a single batch and view the line status summary.
- Use the "Copy" or "Download" buttons above the output box to export your percent-encoded URL list.
Options Explained
- Encode Space as +: Escapes literal + as %2B before replacing %20 spaces with + on each row (default uses %20).
- Strict RFC 3986: Escapes sub-delimiters !, ', (, ), and * into %21, %27, %28, %29, and %2A on every line.
- Preserve URL Structure: Leaves URI delimiters (:/?&=#+@$,;) unescaped per line so full HTTP links remain valid while encoding UTF-8 text.
Key Features
- Percent-encode up to 100,000 URLs and query strings in one run with a live line counter.
- Keep 1:1 row alignment with blank lines intact, encoding spaces without trimming or %0A line merges.
- Format spaces as + after escaping + into %2B, and encode RFC 3986 sub-delimiters (!'()*) per row.
- Preserve URI delimiters (:/?&=#+@$,;) per line to keep HTTP links valid while escaping spaces and UTF-8 values.
- Encode multi-byte UTF-8 characters, accented letters, global scripts, and 4-byte emojis (%F0%9F%9A%80) across every row.
- Execute all batch URL percent-encoding locally in your browser memory with zero server data storage.
About This Online Bulk URL Encoder
This bulk URL encoder converts up to 100,000 URLs into RFC 3986 percent-encoded strings with 1:1 row order. It prevents %0A line merging and provides toggles for + spaces, strict RFC 3986, and URL structure.
Developed and maintained by the PU Tools team, this tool gives you fast, accurate, safe, and easy results in just a few clicks.
Common Use Cases
- Spreadsheet URL Columns: Convert columns of raw links, search queries, and UTM values into percent-encoded strings per row.
- API and Webhook Lists: Format batches of redirect URLs, callback links, and form query strings for HTTP test suites.
- Multilingual Sitemap Links: Escape spaces and UTF-8 paths across lists of international URLs while keeping URI delimiters intact.
Example Input and Output
Example Input
https://example.com/?q=hello world&tag=C++ https://example.com/?doc=Café Résumé 🚀 https://example.com/?item=Crème (2026)!
Options used: Encode Space as +: OFF | Strict RFC 3986: OFF | Preserve URL Structure: OFF
Example Output
https%3A%2F%2Fexample.com%2F%3Fq%3Dhello%20world%26tag%3DC%2B%2B https%3A%2F%2Fexample.com%2F%3Fdoc%3DCaf%C3%A9%20R%C3%A9sum%C3%A9%20%F0%9F%9A%80 https%3A%2F%2Fexample.com%2F%3Fitem%3DCr%C3%A8me%20(2026)!
The tool percent-encodes each URL line into uppercase %XX UTF-8 bytes while keeping blank rows intact.
Frequently Asked Questions
How many URLs or query strings can I percent-encode in a single batch?
You can percent-encode up to 100,000 URLs in one run with the live line counter. For lists larger than 100,000 rows, divide your data into smaller chunks before clicking the encode button.
How does this bulk URL encoder differ from the single URL encoder when processing multiple lines?
This bulk tool encodes each row independently in 1:1 order without merging lines or adding %0A tokens. Conversely, our single URL encoder strips line breaks to merge wrapped lines into one continuous output string.
How are blank rows and lines with leading, trailing, or space-only characters handled during batch encoding?
Empty lines remain blank at their exact positions to maintain 1:1 row alignment with your spreadsheet columns. Leading, trailing, and space-only characters on a line are never trimmed and encode into %20 or +.
How does encoding spaces as + handle existing + signs on each row for form query strings?
On every row, the encoder escapes literal + symbols into %2B before converting %20 spaces into +. This order formats application/x-www-form-urlencoded queries on each row without corrupting raw + signs in values like C++.
When should I enable strict RFC 3986 mode across a batch list of URLs or parameters?
Turn on strict RFC 3986 when your batch feeds OAuth signatures, canonical API requests, or strict parsers. It escapes sub-delimiters !, ', (, ), and * into %21 through %2A across every row.
When should I preserve URL structure on each row instead of using default full percent-encoding?
Preserve URL structure to keep URI delimiters (:/?&=#+@$,;) intact per row while encoding spaces and UTF-8 text. Use default full encoding when each line is a query parameter value or nested redirect URL.
Does this tool process UTF-8 characters and emojis locally in my browser without server data storage?
Yes, all batch encoding runs 100% locally in your browser memory with zero server data storage. Every row encodes multi-byte UTF-8 scripts and emojis into uppercase %XX hex bytes directly on your device.