Skip to content
New: a free website for your business, live in 48 to 72 hoursWorkflow automation on n8n and Claude, built for your businessFixed price, agreed before we start · Live in 5 to 10 business days30-day money-back guarantee on every planProfessional firms · Agencies · E-commerceYou own every workflow, in your own n8nClaude API: your data is not used for trainingHuman approval on every sensitive stepFree automation audit, no obligation
PURIST
30 days
Money-back window
14 h/wk
Modeled time saved
99.97%
Uptime SLA
< 7 days
Deploy time
PURIST AI
Claude Opus 4.7 · n8n v1.71 · <80ms
What type of business are you running? I'll show you exactly which processes we'd automate first and your estimated ROI.
Powered by n8n + Claude Opus 4.7 Get my free automation plan →

Free Tools /Development

Base64 & URL Encoder / Decoder

Encode or decode Base64 and URL-encoded strings instantly, in both directions, with UTF-8 handled correctly.

  • Free, no signup
  • Runs in your browser
  • Nothing stored

How this tool works

01

Four operations, one input box

Encode to Base64, decode from Base64, encode for a URL, or decode a URL-encoded string, switch between them with the tabs, no page reload.

02

Auto-detect on decode

When decoding, the tool tells you immediately if your input is not valid Base64 or is not URL-encoded, rather than silently returning garbage.

03

UTF-8 safe

Handles accented characters and emoji correctly in both directions, unlike a naive atob()/btoa() call which breaks on non-ASCII text.

Frequently asked questions

When do I need Base64 encoding in an automation workflow?

Most commonly for HTTP Basic Authentication headers (which require "username:password" Base64-encoded), for embedding small binary data like images in JSON payloads, and for some webhook signature schemes that expect a Base64-encoded HMAC.

What is the difference between Base64 encoding and encryption?

Base64 is not encryption or security, it is a reversible encoding scheme with no secret key. Anyone can decode Base64 instantly, as this tool demonstrates. Never use Base64 alone to protect sensitive data.

When do I need URL encoding instead of Base64?

URL encoding (percent-encoding) is for characters that are not safe inside a URL, like spaces, ampersands, or special symbols in a query string parameter. Base64 output itself often needs URL encoding too if you are passing it as a URL parameter, since Base64 can include characters like "+" and "/" that have special meaning in URLs.

Why did my decode fail with an error?

Base64 decode fails if the input length is not a multiple of 4 (after removing valid padding) or contains characters outside the Base64 alphabet (A-Z, a-z, 0-9, +, /, =). URL decode fails on a malformed percent-sequence, like a "%" not followed by two hex digits.

Is this safe to use for actual passwords or secrets?

The encoding/decoding happens entirely in your browser and nothing is transmitted, but as a general practice avoid pasting real production secrets into any browser tool when a local script or your terminal can do the same job just as fast.

Done for you

Want this running inside your business, automatically?

We build the workflow behind tools like this one, wired to your CRM, inbox and apps, and keep it running. Fixed price, from $390 a month.