# How I URL-encode text without breaking query strings

A beginner-friendly guide to percent encoding, query parameters, reserved characters, and safe URL decoding.

- Date: 2026-09-27
- URL: https://ilham.dev/posts/how-to-url-encode-text-without-breaking-query-strings/
- Markdown: https://ilham.dev/posts/how-to-url-encode-text-without-breaking-query-strings/index.md
- Tags: url, encoding, web, tools
- Reading time: 2 min


URLs can only safely contain certain characters. URL encoding turns spaces, symbols, and non-ASCII text into percent-encoded form.

The [URL Encoder](/tools/url-encoder/) tool helps with the mechanical part, but I still check the result before using it somewhere real.

## The simple idea

URLs can only safely contain certain characters. URL encoding turns spaces, symbols, and non-ASCII text into percent-encoded form.

I use the tool to make the transformation visible: input on one side, output on the other, and a quick sanity check before I copy anything.

## Step 1: Decide whether you are encoding a whole URL or one parameter value

Decide whether you are encoding a whole URL or one parameter value.

## Step 2: Encode parameter values separately when building query strings

Encode parameter values separately when building query strings.

## Step 3: Check spaces, ampersands, question marks, and equals signs

Check spaces, ampersands, question marks, and equals signs.

## Step 4: Decode the result to confirm it returns to the original text

Decode the result to confirm it returns to the original text.

## Step 5: Do not double-encode an already encoded value

Do not double-encode an already encoded value.

## Step 6: Be careful decoding URLs that contain tokens

Be careful decoding URLs that contain tokens.

## Step 7: Use a URL parser when debugging a full URL structure

Use a URL parser when debugging a full URL structure.

## My checklist

Before I trust the result, I check:

- Decide whether you are encoding a whole URL or one parameter value.
- Encode parameter values separately when building query strings.
- Check spaces, ampersands, question marks, and equals signs.
- Decode the result to confirm it returns to the original text.
- Do not double-encode an already encoded value.
- Be careful decoding URLs that contain tokens.
- Use a URL parser when debugging a full URL structure.

Small utilities are useful because they remove repetitive work. They are safest when the output is still reviewed.