Put it to work
Encode 안녕하세요 as UTF-8 Base64, then decode it back to the original text.
From input to output
- Open Encoding converter and load the example.
- Read the format notes, choose your options, and replace the example with your input. Start with test data instead of sensitive information.
- Run the tool and inspect the result and status. If an error appears, correct the input format and run it again.
- Copy the output or download a file. Generated and converted results are not saved automatically.
Spaces and plus signs in URLs
Component encoding turns a space into %20 and a plus sign into %2B. Decoding does not treat a literal + as a space. The application/x-www-form-urlencoded format has a separate rule that does, so distinguish these formats. Base64 represents UTF-8 bytes as text. If decoded bytes are binary data rather than valid UTF-8, this text tool reports an error.
Example input
hello + world
Reading the result
URL component: hello%20%2B%20world Base64: aGVsbG8gKyB3b3JsZA==
Details that matter
Format and meaning
Base64 is encoding, not encryption, and does not protect secrets.
Using it correctly
URL encoding applies to individual components, such as query values, not an entire URL.
Common pitfalls
Unicode output uses UTF-16 \uXXXX escapes. An emoji may use two code units.
Supported scope and limits
1 MB UTF-8 text
Split inputs that exceed the limit. If a format or algorithm is unsupported, choose a tool that matches your requirements instead of silently changing the format.
What happens to your data?
Tools run in your browser. DNS lookup sends the queried domain to the named external provider. Ads may appear on home, guide, and workspace pages according to settings.
Open tool