Base64, URL, and HTML Encoder/Decoder
String encoding converts text from one format to another. Developers use it daily when working with APIs, URLs, HTML, and data transmission. The FlipMyCase String Encoder handles the three most common formats.
How to Use the String Encoder
- Open the FlipMyCase String Encoder.
- Select the encoding type: Base64, URL, or HTML.
- Paste your input string.
- Switch between Encode and Decode modes.
- Copy the result.
Base64 Encoding
Base64 converts any data into a string of printable ASCII characters. Common uses:
- Data URIs: Embed small images directly in HTML:
<img src="data:image/png;base64,..."> - API payloads: Send binary files in JSON request bodies
- Authentication headers: HTTP Basic Auth encodes
username:passwordin Base64 - Email: MIME encoding uses Base64 for attachments
Example
| Input | Base64 | |---|---| | Hello World | SGVsbG8gV29ybGQ= | | user:pass123 | dXNlcjpwYXNzMTIz |
URL Encoding
URL encoding makes text safe for use in URLs. Characters outside the basic ASCII set and reserved characters are converted to percent-encoded format.
When You Need It
- Building query strings:
?search=hello%20world&lang=en - Encoding file names in download URLs
- Passing special characters in API parameters
- Encoding redirect URLs within other URLs
Common Conversions
| Character | Encoded | |---|---| | (space) | %20 | | & | %26 | | = | %3D | | / | %2F | | @ | %40 |
HTML Entity Encoding
HTML entity encoding prevents browsers from interpreting your text as HTML tags. Essential for displaying code examples, user-generated content, and special characters.
When You Need It
- Displaying
<script>tags as text on a web page - Sanitizing user input to prevent XSS attacks
- Showing code examples in tutorials
- Using special characters like ©, ™, and €
Common Conversions
| Character | Entity | |---|---| | < | < | | > | > | | & | & | | " | " | | ' | ' |
Security Note
Encoding is not encryption. Base64, URL encoding, and HTML entities are all reversible by anyone. They exist for data formatting and compatibility, not security. For protecting sensitive data, use proper encryption algorithms.