The result differs from another encoder
compare delimiter, quoting, BOM, text encoding and CRLF/LF line endings.
Convert TSV to Base64
Encode TSV as standard or URL-safe Base64 while preserving the source representation. Review, copy or download the result.
Base64 utility · Fast, exact Base64 conversion
What this tool does
This page encodes TSV into Base64 without applying format-specific validation or transformation. Use Standard or URL-safe output according to the receiving protocol, then copy or download the value.
Convert now
1
Enter or upload
Paste text or choose a file
2
Choose an action
Encode, decode or inspect
3
View results
Review output and byte details
1. Input
0 characters
2. Action
3. Output
0 characters
4. Quick actions
5. Base64 information
DescriptionBase64 represents bytes as text; it is not encryption.
AlphabetA-Z, a-z, 0-9, +, /, =
Input size0 characters / 0 bytes
Output size0 characters / 0 bytes
PaddingUses = to complete a four-character group.
StatusReady
How it works
Input bytes
101010 111100 110101 ...
Split into 6-bit groups
101010 111100 110101 ...
Convert to indexes
42 60 53 ...
Base64 characters
q 8 1 ...
How to convert TSV to Base64
Paste the TSV source exactly as it should be encoded.
Keep Encode selected and choose the output option shown by the tool.
Review the output and byte information, then copy or download the result.
Output and format behavior
Tabs and line breaks remain part of the source bytes. The converter does not validate column counts or normalize data copied from a spreadsheet.
Use Standard Base64 for the normal RFC 4648 alphabet. Use URL-safe only when the receiving system expects Base64URL; padding rules can differ by protocol.
Expert tip
Document the delimiter, line ending and character encoding beside the payload so another system can reconstruct the same table dialect.
When this is useful
Typical workflows include:
- Preserve delimiters, tabs and line endings when moving table text through a field that otherwise alters whitespace.
- Place a value in a configuration field that accepts text but not arbitrary bytes or line breaks.
- Create a reproducible test fixture without manually rewriting the source bytes.
Limitations and safety
Important constraints:
- Base64 normally adds about one third to the byte payload, before any data-URL prefix or surrounding markup.
- Base64 is reversible encoding, not encryption. Anyone who receives the string can decode the original bytes.
- The converter preserves the supplied table text; it does not detect delimiters, normalize rows, infer types or repair malformed data.
Troubleshooting
Rows look different after decoding elsewhere
verify that the receiving application uses the same delimiter and character encoding.
Frequently asked questions
What exactly is preserved?
Tabs and line breaks remain part of the source bytes. The converter does not validate column counts or normalize data copied from a spreadsheet.
Does this page validate the source format?
No. It converts the supplied text or bytes. Use a dedicated parser, formatter or validator when syntax correctness matters.
What is the difference between standard Base64 and Base64URL?
Standard Base64 uses + and /. Base64URL uses - and _ and may omit padding; choose the form required by the receiving system.
Do delimiters, BOM and line endings affect the output?
Yes. Tabs, commas, quoting, BOM and CRLF/LF are encoded as supplied, so they must be kept consistent when comparing results.
Related Base64 tools
Continue with the localized page that matches the next operation:
Paste your input above, run the conversion, and copy or download the result.