Stego Encoder

Hide text or small files inside images using Least Significant Bit encoding. The output looks identical to the original — invisible to the naked eye.

Drag & drop a file here, or

PNG BMP WebP Lossless formats only • PNG recommended • Processed in browser

Invisible Encoding

Modifies only the least significant bit of each pixel — changes are invisible to the human eye.

Lossless PNG Output

Output is always PNG to preserve LSB data. JPEG compression would destroy the hidden content.

100% Private

All encoding runs in your browser using the Canvas API. Your images and data never leave your device.

How it works

How LSB steganography encoding works

The Stego Encoder converts your message into a stream of bits and writes each bit into the least significant bit of a pixel's color channel (Red, Green, or Blue). Changing a pixel value from 200 to 201 — or from 201 to 200 — produces zero visible difference, yet each pixel stores one bit of your hidden data across its three channels. A 1000×1000 image holds roughly 375 KB of hidden data. The output is always PNG because lossless compression preserves exact pixel values; JPEG would destroy the embedded bits during encoding. To verify that the encoding worked, run the output through the Stego Scanner.

Security and password protection

The optional password applies XOR encryption to the payload before embedding. Without the password, the extracted bits look like random noise rather than readable text. This adds a layer of protection, though XOR is not cryptographically strong — for sensitive data, encrypt it externally before embedding. The Image Encryption tool can lock the entire image with AES. Since all processing runs in your browser, your data never touches a server — verify this with the File Hash Scanner to confirm the original and encoded images produce different hashes.

Who uses steganography encoding

Cybersecurity students and CTF competitors practice steganography challenges by encoding and extracting hidden flags. Photographers embed invisible copyright watermarks that survive casual sharing but can be extracted to prove ownership — combine this with the Image Watermark tool for visible branding. Privacy-conscious users share sensitive text through ordinary-looking photos rather than plaintext messages. Researchers studying information hiding embed test payloads and then analyze them with the Bit Plane Viewer to visualize the encoding footprint.

Choosing the right cover image

Larger images hold more data, but a good cover image also has complex, noisy content — photographs of nature, cityscapes, or textured surfaces make LSB modifications harder to detect statistically. Solid-color or gradient images are poor choices because their pixel patterns are highly predictable, making embedded data easier to spot via the Noise Analysis tool. Always use lossless formats (PNG, BMP) — converting to JPEG afterward destroys the hidden data. If your cover is too small, resize it first with the Image Resizer.

The Stego Encoder is the companion tool to the Stego Scanner: encode a message here, then verify the output with the scanner to confirm the data is properly embedded. Together they form a complete steganography workflow — all running privately in your browser with no data ever sent to a server. For a deeper understanding of steganography techniques and detection methods, read our steganography explained guide.

Frequently Asked Questions

How does this steganography encoder work?
The encoder converts your text or file into a stream of bits and writes each bit into the least significant bit (LSB) of the image's color channels (Red, Green, Blue). This changes each pixel value by at most 1 out of 255 — invisible to the human eye. The output is saved as PNG to preserve the exact pixel values.
How much data can I hide in an image?
Each pixel stores 3 bits of hidden data (one per color channel), so the maximum capacity is width × height × 3 ÷ 8 bytes, minus a small header. A 1920×1080 image can hold roughly 770 KB. Larger images hold more data — the tool shows exact capacity after you upload.
Why is the output always PNG?
PNG uses lossless compression that preserves exact pixel values, including the modified least significant bits. JPEG, WebP lossy, and other lossy formats alter pixel values during compression, which would destroy the hidden data. Always share the encoded image as PNG — never convert it to JPEG.
Is the password encryption secure?
The built-in password uses XOR encryption, which obscures the hidden data from casual inspection but is not cryptographically strong. For sensitive information, encrypt your data with a proper tool (AES, GPG) before pasting it into the encoder. The XOR option is useful for CTF challenges and casual privacy.
Can I embed files, not just text?
Yes. Switch to "File" mode and upload any file smaller than the image capacity. The file name is preserved in the encoded data, so the recipient can extract the original file with its name intact using a compatible steganography decoder.
Is my data uploaded to a server?
No. All encoding runs entirely in your browser using the Canvas API. Your images, text, files, and passwords never leave your device — nothing is transmitted, stored, or logged. This makes it safe to encode sensitive information.