Kisimbaji / Kisimbuaji cha Base64

Simba maandishi au faili kuwa Base64, au simbua Base64 kurudi. Lahaja ya URL-safe, salama kwa UTF-8, upande wa mteja tu.

URL-safe (-_) Bila padding

Upangaji wa mistari

Ingizo

0 vibambo

Matokeo yaliyosimbuliwa

0 vibambo

Kwa nini Base64?

Haraka, sahihi, na kila chaguo unalohitaji.

Simba na simbua

Geuza maandishi au faili yoyote kuwa Base64, au simbua Base64 kurudi kwa data asili. Onyesho la papo hapo unapoandika.

Faragha kwa muundo

Usimbaji na usimbuaji wote hufanyika katika kivinjari chako. Maandishi na faili zako hazijawahi kupakiwa kwenye seva yoyote.

Faili na data URLs

Dondosha faili yoyote kupata mfuatano wake wa Base64, data URL (data:mime;base64,…), au simbua mfuatano wa Base64 kurudi kuwa faili ya binari.

Lahaja ya URL-safe

Washa Base64 ya URL-safe (Base64URL, RFC 4648) — hubadilisha + kuwa - na / kuwa _ kwa matumizi katika URLs, majina ya faili, JWT, n.k.

Salama kwa UTF-8

Usaidizi kamili wa Unicode kwa lugha yoyote, emoji, CJK, hati za RTL. Hutumia TextEncoder/TextDecoder ili kusiwe na uharibifu.

Upangaji wa mistari na padding

Upangaji wa hiari wa mistari wa mtindo wa MIME kwa vibambo 64 au 76, na uondoaji wa hiari wa padding — kwa saini, cookies, tokeni fupi.

How Base64 encoding works in your browser

Native browser APIs, no upload, lossless round-trip for any text or file.

1

Pick text or file mode

Toggle between text mode (paste any string) and file mode (drop any file up to ~50 MB). Text is processed via TextEncoder for proper UTF-8 handling — emoji and non-ASCII characters round-trip correctly. Files are read as ArrayBuffer.
2

Encoder runs locally

JavaScript's built-in btoa encodes the bytes to Base64. For URL-safe variant we replace + with - and / with _, and optionally strip padding (the format JWT uses). For very large files we chunk encoding to avoid blocking the main thread.
3

Decoder is the inverse

Paste a Base64 string and we run atob to decode. If you encoded a binary file originally, we offer a download with the original MIME type; if you encoded text, we decode it back via TextDecoder. Both directions are lossless.
4

Copy, download, or generate a Data URI

One-click copy puts the Base64 on your clipboard. Or download as a .txt file. Or generate a data:image/png;base64,... URI for inline embedding in CSS / HTML — assembled in your browser.

Common Base64 workflows

What people actually use Base64 for, and how iKit fits in.

Embedding small images in CSS

Convert a 2 KB icon to a Data URI to inline it in a stylesheet — saves an HTTP request. iKit produces the full data:image/png;base64,... string ready to paste.

JWT debugging

Decode the middle segment of a JWT to inspect the claims. Pair this with iKit's JSON Decoder for a clean two-step debugging flow that never sends the token to a server.

Email attachments via API

When a transactional email API requires Base64-encoded attachments, drop the file into iKit, copy the result, paste into your request body. No CLI base64 dance, no platform differences (macOS vs Linux flags).

PEM keys and certificates

Decode a PEM block (after stripping the BEGIN/END lines) to inspect the raw DER bytes. Or encode a binary key into PEM for tools that only accept text format.

Why Base64 privacy is non-negotiable

Base64 is the default carrier for sensitive payloads — JWTs containing user IDs and permissions, embedded customer photos, internal API responses. A server-side Base64 tool sees every byte you paste. iKit's encoder runs purely in JavaScript, so nothing leaves your browser tab.

Zero fetch or XHR calls during encode or decode.
Files up to ~50 MB processed locally without upload.
Lossless round-trip — encode then decode returns the exact original bytes.

Miongozo inayohusiana

Mafunzo ya kina na ulinganishaji wa zana kutoka blogu ya iKit.

How to Encode and Decode Base64 — With Real Examples

Base64 in the wild: data URLs, JWT, email attachments, and the most common decode pitfalls.

Maswali Yanayoulizwa Mara kwa Mara

Je, ingizo langu linatumwa kwa seva?

Hapana. Usimbaji na usimbuaji wote hufanyika katika kivinjari chako kwa kutumia APIs za ndani za JavaScript (TextEncoder, btoa, atob). Hakuna kinachopakiwa, kuwekwa kumbukumbu, au kuhifadhiwa.

Base64 ya URL-safe ni nini?

Base64 ya kawaida hutumia + na / ambavyo vina maana maalum katika URLs. Base64 ya URL-safe (RFC 4648 §5) huvibadilisha kuwa - na _ mtawalia, ili matokeo yawe salama kutumia katika URLs, majina ya faili, na tokeni kama JWT.

Je, inashughulikia Unicode / emoji kwa usahihi?

Ndiyo. Tunatumia TextEncoder kubadilisha maandishi yako kuwa baiti za UTF-8 kabla ya kusimba, na TextDecoder kubadilisha baiti zilizosimbuliwa kurudi. Kibambo chochote cha Unicode — CJK, emoji, hati za RTL — kinasafiri kikamilifu.

Je, naweza kusimba faili kama PDFs au picha?

Ndiyo. Badilisha hadi hali ya Faili na udondoshe faili yoyote. Zana itakupa mfuatano wa Base64, data URL unayoweza kubandika katika HTML/CSS, au upakuaji wa.txt. Ukubwa wa faili unategemea kumbukumbu ya kivinjari (kwa kawaida hufanya kazi hadi mamia ya MB).

Tofauti kati ya na bila padding ni nini?

Base64 ya kawaida hupamba matokeo na vibambo vya '=' ili urefu wake uwe mzidisho wa 4. Matumizi mengine (JWT, tokeni za URL) huondoa padding kuokoa nafasi; kisimbuaji kinaweza kuijenga upya. Chagua 'Bila padding' kuondoa = za mwisho.