Aman untuk UTF-8
Menangani teks internasional tanpa merusak karakter.
Encoder/Decoder Base64
Encode teks ke Base64 atau decode Base64 kembali menjadi teks UTF-8 yang terbaca. Mendukung Base64 standar dan URL-safe, semuanya berjalan di browser.
Iklan
Iklan
Encode dan dekode Base64 tanpa mengunggah data Anda
Dukungan UTF-8 penuh, mode URL-safe, dan konversi real-time — langsung di browser Anda. Tanpa unggah, tanpa daftar, tanpa batas.
100% pribadi
UTF-8 safe
Gratis selamanya
Cara menggunakan
- 1
Tempel teks
Masukkan teks biasa untuk encode atau tempel string Base64 untuk decode.
- 2
Pilih format
Gunakan Base64 standar untuk data umum dan URL-safe untuk token atau query string.
- 3
Encode, decode, atau salin
Jalankan konversi lalu salin hasilnya.
Mengapa memakai alat Base64 ini?
Mode URL-safe
Menyesuaikan karakter dan padding untuk konteks web.
Hanya di browser
Berguna untuk snippet, token, dan nilai konfigurasi privat.
Iklan
Memahami Encoding Base64
Apa itu Base64 dan mengapa menggunakannya?
Base64 is an encoding scheme that converts binary data into a text representation using 64 ASCII characters (A-Z, a-z, 0-9, +, /). The encoding process takes every 3 bytes of input and converts them into 4 Base64 characters. This ensures that any binary data — including images, executables, and encrypted bytes — can be safely transmitted through channels that only support text, such as email, JSON, XML, and URLs.
The most common use cases for Base64 are: embedding binary data in JSON or XML (where raw bytes would break the syntax), encoding images as data URIs in HTML/CSS, encoding JWT token payloads, transmitting credentials in HTTP Basic Auth headers, and storing binary data in text-based databases or configuration files.
Iklan
Standard vs. URL-safe Base64
Standard Base64 uses + and / as two of its 64 characters. These characters have special meanings in URLs (+ means space, / is a path separator), which can cause problems when Base64 strings appear in URLs or file names. URL-safe Base64 (RFC 4648 §5) replaces + with - and / with _, and typically omits the = padding character.
JWT tokens use URL-safe Base64 for encoding the header and payload. If you try to decode a JWT payload with standard Base64, you may get an error because - and _ are not valid standard Base64 characters. Our tool handles both formats — simply toggle the URL-safe option to match your input.
Base64 bukan enkripsi
Base64 provides no security or confidentiality. Anyone who has the Base64 string can decode it back to the original data in milliseconds. Never use Base64 to protect passwords, API keys, or other secrets. If you need to protect data, use a proper encryption algorithm like AES-256. Base64 is only useful for ensuring data compatibility across systems, not for security.
Iklan
Kasus Penggunaan Umum
Real-world scenarios where a Base64 encoder/decoder is essential.
JWT Tokens
Decode JWT header and payload by Base64-decoding each part. Essential for debugging authentication flows.
Data URIs
Encode images, fonts, or small files as Base64 data URIs for embedding directly in HTML, CSS, or JSON.
Configuration Files
Encode binary data or special characters in YAML, JSON, or XML configuration files where raw bytes are not allowed.
API Credentials
Encode API keys and secrets for HTTP Basic Auth headers or other credential-passing mechanisms.
Bagaimana ini dibandingkan dengan alat Base64 lain?
A side-by-side comparison of popular Base64 encoding tools.
| Fitur | NovaTools | Base64Encode.org | Browser btoa() |
|---|---|---|---|
| Privasi (tanpa unggah) | 100% lokal | Unggah ke server | Lokal |
| Mode aman URL | Manual | ||
| Dukungan UTF-8 | btoa() fails on non-ASCII | ||
| Konversi real-time | Klik tombol | N/A | |
| Auto-detect mode | N/A | ||
| Ramah mobile | Terbatas | N/A | |
| Berfungsi offline | Setelah halaman dimuat |
Base64Encode.org mengunggah data Anda ke server mereka. Alat kami memproses semuanya secara lokal — teks Anda tidak pernah meninggalkan browser Anda.
Base64 Quick Reference
Key facts about Base64 encoding.
Character Set
| Simbol / Kode | Deskripsi | Contoh |
|---|---|---|
A-Z | Uppercase letters (26 characters). | QUJDRA== (encodes ABCD) |
a-z | Lowercase letters (26 characters). | YWJjZA== (encodes abcd) |
0-9 | Digits (10 characters). | MDEyMzQ= (encodes 01234) |
+ / | Standard Base64 special characters. + becomes - and / becomes _ in URL-safe mode. | Pj8+Pw== (encodes >?>?) |
= | Padding character (0-2 at end). Omitted in URL-safe mode. | aGk= (encodes hi, 1 pad) |
A-ZUppercase letters (26 characters).
Contoh:
QUJDRA== (encodes ABCD)a-zLowercase letters (26 characters).
Contoh:
YWJjZA== (encodes abcd)0-9Digits (10 characters).
Contoh:
MDEyMzQ= (encodes 01234)+ /Standard Base64 special characters. + becomes - and / becomes _ in URL-safe mode.
Contoh:
Pj8+Pw== (encodes >?>?)=Padding character (0-2 at end). Omitted in URL-safe mode.
Contoh:
aGk= (encodes hi, 1 pad)Key Facts
| Simbol / Kode | Deskripsi | Contoh |
|---|---|---|
3 → 4 | Every 3 input bytes become 4 Base64 characters. | abc → YWJj (3 bytes → 4 chars) |
33% | Base64 output is approximately 33% larger than input. | 300 bytes → 400 chars |
UTF-8 | Text is encoded as UTF-8 bytes before Base64 encoding. | é → w6k= (2 UTF-8 bytes) |
Not encryption | Base64 provides no security. Anyone can decode it. | dGVzdA== → test (instantly reversible) |
3 → 4Every 3 input bytes become 4 Base64 characters.
Contoh:
abc → YWJj (3 bytes → 4 chars)33%Base64 output is approximately 33% larger than input.
Contoh:
300 bytes → 400 charsUTF-8Text is encoded as UTF-8 bytes before Base64 encoding.
Contoh:
é → w6k= (2 UTF-8 bytes)Not encryptionBase64 provides no security. Anyone can decode it.
Contoh:
dGVzdA== → test (instantly reversible)Pertanyaan yang sering diajukan
Base64 digunakan untuk apa?
Base64 mengubah teks atau data biner menjadi karakter ASCII agar aman digunakan di JSON, URL, email, token, dan file konfigurasi.
Apakah mendukung teks Unicode?
Ya. Alat ini memakai UTF-8, sehingga aksen, emoji, dan teks multibahasa dapat diproses dengan benar.
Apakah teks saya diunggah ke server?
Tidak. Semua konversi berjalan lokal di browser dan input Anda tidak meninggalkan perangkat.
Untuk apa encoding Base64 digunakan?
Base64 turns binary or text data into ASCII characters so it can safely travel through JSON, URLs, emails, tokens, and configuration files. It is commonly used to embed images in CSS/HTML (data URIs), encode JWT payloads, transmit binary data over text-only protocols, and store binary blobs in databases that only support text. Base64 is not encryption — it provides no security or confidentiality. Anyone can decode Base64 back to the original data.
Apakah alat ini mendukung teks Unicode?
Yes. The encoder uses UTF-8, so text with accents, emoji, Chinese, Japanese, Korean, and other scripts can be encoded and decoded correctly. The tool first converts the input string to a UTF-8 byte sequence, then encodes those bytes to Base64. On decode, it reverses the process. This avoids the common 'btoa() does not work with non-ASCII characters' error that occurs when using the native browser btoa() function directly.
Apakah teks saya diunggah ke server?
No. Encoding and decoding happen locally in your browser with JavaScript. Your input never leaves your device. You can verify this by opening your browser's DevTools Network tab — no network requests are made when you encode or decode. This makes the tool safe for encoding API keys, tokens, credentials, and other sensitive data.
Apa perbedaan antara Base64 standar dan URL-safe?
Standard Base64 uses the characters A-Z, a-z, 0-9, +, and /, and pads the output with = characters. The + and / characters can cause problems in URLs and file names. URL-safe Base64 replaces + with - and / with _, and typically omits the = padding. URL-safe Base64 is used in JWT tokens, data URIs, and other contexts where the encoded string appears in a URL or file name. Our tool lets you toggle between standard and URL-safe modes.
Bisakah saya mengodekan file biner (gambar, PDF)?
This tool is designed for text encoding and decoding. For binary files, use a tool that reads the file as an ArrayBuffer and converts it to Base64. However, you can use this tool to decode a Base64 string that represents a binary file (like a data URI) and inspect the MIME type. For encoding images as Base64 data URIs, our Image Converter tool handles this automatically.
Mengapa string Base64 saya tidak didekode dengan benar?
The most common cause is a character encoding mismatch. If the original text was encoded as UTF-8 but decoded as Latin-1 (ISO 8859-1), non-ASCII characters will appear garbled. Another common issue is URL-safe Base64 being decoded as standard Base64 (or vice versa) — the - and _ characters are not valid in standard Base64. Make sure you select the correct mode (standard or URL-safe) for your input. Finally, check that the input string has the correct length — Base64 strings should have a length that is a multiple of 4 (after padding).
Apakah Base64 enkripsi?
No. Base64 is an encoding scheme, not encryption. Encoding converts data from one format to another using a publicly known algorithm, and anyone can decode it. Encryption uses a secret key to scramble data so that only someone with the key can read it. Never use Base64 to protect sensitive data — use proper encryption (AES, RSA) instead. Base64 is only useful for ensuring data compatibility across systems that handle text differently.
Seberapa lebih besar Base64 dibandingkan data asli?
Base64 encoding increases data size by approximately 33%. Every 3 bytes of input becomes 4 characters of Base64 output. For example, a 300-byte input produces a 400-character Base64 string. This overhead is the trade-off for ensuring the encoded data contains only ASCII characters that are safe to transmit over text-only channels. If bandwidth is critical, consider using a binary format instead of Base64.
Apakah alat ini berfungsi di perangkat seluler?
Ya. Alat ini sepenuhnya responsif dan berfungsi di iOS Safari dan Android Chrome. Mode AI memerlukan perangkat yang relatif kuat — ponsel kelas menengah dari 2-3 tahun terakhir menanganinya dengan baik, tetapi perangkat lama mungkin lambat atau kehabisan memori. Mode Color Key berfungsi di semua perangkat, termasuk ponsel lama. Di seluler, Anda dapat memilih gambar dari pustaka foto, kamera, atau aplikasi penyimpanan cloud.
Bisakah saya menggunakan ini untuk proyek komersial?
Ya. Alat ini gratis untuk penggunaan pribadi dan komersial tanpa watermark, tanpa atribusi yang diperlukan, dan tanpa batasan penggunaan. Anda mempertahankan kepemilikan penuh atas gambar yang diproses. Model AI yang mendasari (MediaPipe) dilisensikan oleh Google untuk penggunaan komersial. Tidak ada pendaftaran, tidak ada API key, dan tidak ada langganan yang diperlukan.
Privasi Anda Adalah Prioritas Kami
Alat ini berjalan sepenuhnya di browser Anda. File Anda tidak diunggah ke server, tidak disimpan, dan tidak dianalisis.
- Kami tidak mengunggah, menyimpan, atau menganalisis file Anda.
- Semua yang Anda proses tetap di perangkat Anda.
- Tidak ada pemrosesan sisi server, penyimpanan cloud, atau analisis.
Bahkan jika koneksi internet Anda terputus, file Anda tetap aman.
Anda mungkin juga suka
Jelajahi topik ini
Panduan terkait
Cara encode dan decode teks Base64 dengan aman
Pelajari apa itu Base64, kapan memakai Base64 standar atau URL-safe, dan cara encode/decode teks secara lokal di browser.
Cara Mendekode Token JWT (Header, Payload, Signature)
Pelajari cara mendekode token JWT, memahami header, payload, dan signature, serta arti klaim iat, nbf, dan exp. Bedakan dekode vs verifikasi. 100% sisi klien.
10 Alat Produktivitas Pengembang Gratis yang Benar-Benar Menghemat Waktu
Temukan alat pengembang gratis terbaik yang meningkatkan produktivitas tanpa menghabiskan banyak uang. Dari pemformat kode hingga penguji API, alat-alat ini akan menyederhanakan alur kerja Anda.
Iklan