TYOHILIAHide Like A Pro

Hide & reveal

Steghide's core loop: put a file inside an image, get it back later. The image in between looks and behaves like a normal picture.

Hiding

In the Hide panel:

  1. Carrier image — the picture that will carry your data. PNG and BMP carriers preserve every pixel; JPEG carriers work through the compressed coefficients. Bigger, busier images hold more — check with Capacity.
  2. Payload — any file at all. It's stored byte-for-byte and comes back identical.
  3. Method — see Choosing a hiding method. The wrong method for your image format is the most common cause of errors.
  4. Passcode — optional, strongly recommended. Without one, anyone who suspects the image and has HILIA can pull the payload out.

Click Hide, then download the stego image. That download is the artefact — HILIA doesn't keep it.

Sending the image safely

The hidden data lives in the fine detail of the pixels, so anything that re-encodes the image destroys it:

Heads up

Most chat apps and social platforms re-compress images on upload, which wipes the payload. Send the stego image as a file/document attachment, not as an inline photo — or zip it first. Screenshots, resizes, crops and format conversions also destroy the payload.

Email attachments, cloud-drive links and "send as file" options in messengers all preserve the bytes and are safe.

Revealing

In the Reveal panel, drop the stego image and enter the passcode used at hide time. The original file downloads with its content intact.

If Reveal fails, the usual causes in order: the image was re-compressed in transit, the passcode is wrong, or the file was never a HILIA stego image — see Troubleshooting.

What HILIA stores

Your images and payloads are processed in memory to perform the operation and are not kept. Usage is metered per operation for gas and stats purposes — not the content. Details in the privacy policy.