What does this actually encode?

Each integer is first turned into the single character it represents as a Unicode code point, then that character is percent-encoded the same way encodeURIComponent would encode it inside a URL.

Why the same range validation as the HTML entity tools?

Both tools treat the integer as a raw Unicode code point, so the same rules apply: it must be within 0-0x10FFFF and outside the UTF-16 surrogate range (0xD800-0xDFFF).

What does a simple ASCII letter encode to?

Unreserved ASCII characters like letters and digits aren't percent-encoded by encodeURIComponent, so they come out unchanged.

How do I reverse this?

Use the companion Integer URL Decoder to turn a percent-encoded string back into its integer code point.

Integer URL Encoder - Code Point to Percent-Encoding

Overview

Introduction

This tool converts a list of integers, each treated as a Unicode code point, into the percent-encoded form of the character it represents, exactly as it would appear inside a URL.

It combines two steps in one pass: turning a code point into a character, then percent-encoding that character with the same rules browsers and JavaScript's `encodeURIComponent` use.

What Is Integer URL Encoder?

A converter that takes a list of integers, one per line, and outputs each one's percent-encoded character representation.

Each integer is interpreted as a Unicode code point, converted to its character with `String.fromCodePoint`, and then percent-encoded.

How Integer URL Encoder Works

Each line is parsed as a whole number and validated to be within 0-0x10FFFF and outside the surrogate range 0xD800-0xDFFF.

The valid code point is converted into its character using `String.fromCodePoint`.

That character is percent-encoded with `encodeURIComponent`, which leaves unreserved ASCII characters unchanged and encodes everything else as %XX bytes.

When To Use Integer URL Encoder

Use it to see exactly how a specific Unicode character would appear once percent-encoded in a URL, starting from just its code point.

It's also useful for building test URLs containing specific encoded characters.

Often used alongside Integer URL Decoder and Integer to HTML Entity Converter.

Features

Advantages

Handles the full Unicode range, not just ASCII, since it goes through a real code point-to-character conversion first.
Uses the same encoding rules as JavaScript's own `encodeURIComponent`, so results match what browsers produce.

Limitations

Rejects surrogate-range code points, since they can't be converted to a standalone character.
Only handles a list of code points, not encoding of longer text strings directly.

Examples

ASCII letter (unreserved)

Input

Output

Non-ASCII character

Input

Output

%C3%A9

Best Practices & Notes

Best Practices

If you're encoding a full word or sentence rather than individual code points, use a general-purpose URL/text encoder instead of feeding it through one code point at a time.

Developer Notes

Uses `encodeURIComponent(String.fromCodePoint(n))`, so multi-byte UTF-8 characters correctly expand into multiple %XX sequences, matching standard URL percent-encoding behavior.

Integer URL Encoder Use Cases

Seeing the percent-encoded form of a specific Unicode code point
Building test URLs containing specific encoded characters
Teaching how percent-encoding interacts with non-ASCII Unicode characters

Common Mistakes

Expecting every code point to produce a %XX sequence; unreserved ASCII characters pass through unchanged.
Entering a surrogate-range value, which is rejected since it isn't a standalone code point.

Tips

Use the companion Integer URL Decoder to confirm a percent-encoded value round-trips back to the same code point.

Integer URL Encoder