◆ Recipe · 2 steps
Make a URL-safe token
Base64-encode with the URL-safe alphabet, then percent-encode the value for a query string.
Why this recipe exists. Standard Base64 adds + and /, which a URL or a query string will mangle. This chain produces a token that survives the trip, in the order that keeps it intact.
01 Sequence
The steps
Each step is a live tool. Open it, do the work, then send the result on.
-
Encode the value with the URL-safe alphabet.
TEXT feeds URL Encoder & Decoder
-
Percent-encode the token for a query string.
Send result carries this value to the next step.
02 Proof
A real run
Run by hand in a browser — the same input and output you get here.
Input Value
Starting input
astra/tools?free=true
Step 1 · Base64 Encoder & Decoder
YXN0cmEvdG9vbHM_ZnJlZT10cnVl
Step 2 · URL Encoder & Decoder
YXN0cmEvdG9vbHM_ZnJlZT10cnVl
03 Edges
If it breaks
One concrete edge case per step.
- Base64 Encoder & Decoder: Pasting a value with characters outside A–Z a–z 0–9 + / = is rejected; decode it back to text first if you are unsure what it holds.
- URL Encoder & Decoder: A % that is not followed by exactly two hex digits, such as %2, is named as an incomplete escape instead of being half-decoded.