Base64 標準

Published

In this guide

This standards reference on Base64Encoding explains standards in plain language for developers and everyday users.

Everything important stays private: try the matching converter or tool in your browser — files and tokens are not uploaded.

Read the full English article below for code samples and edge cases, or switch language anytime from the menu. We keep expanding translations from real user feedback.

Try these private tools next

“Base64” is a family of encodings. They all share the same 3-bytes-to-4-characters algorithm but differ in the last two alphabet characters, padding, line wrapping and extra framing.

Standard Chars 62/63 Padding Line length Used in
Standard (RFC 4648 §4) + / required none APIs, JSON, data URIs
MIME (RFC 2045) + / required max. 76 E-mail attachments
PEM (RFC 7468) + / required exactly 64 Certificates, keys
Base64URL (RFC 4648 §5) - _ optional none URLs, JWT, file names
IMAP (RFC 3501) + , none none Mailbox names in modified UTF-7
XML name token / identifier . - / _ : none none XML NMTOKEN and Name values
OpenPGP armor (RFC 4880) + / required max. 76 PGP messages, with CRC-24 checksum

Not sure which one you have? Use the standard detector, then convert between them with normalization.

常見問題

Does this page upload my data?

No. Articles are static. Linked tools run locally in your browser unless a feature explicitly needs a network relay.

Can I request a translation or a new tool?

Yes — use the private feedback form. We prioritize what users ask for across languages.

What is the fastest way to try standards?

Open the homepage Base64 converter or the related tools linked on this page and paste a sample.

相關工具與指南

留言 (0)

對「Base64 標準」有問題、想法或發現錯誤嗎?歡迎留言、為工具評分或回覆他人。

目前還沒有留言,歡迎搶先分享您的意見!

發表留言

為此工具評分:
Esc
↑ ↓ 移動↵ 開啟Esc 關閉