Guide · Encryption
What does an encrypted file look like? Ciphertext, opened up
An encrypted file looks like random noise: a run of bytes with no pattern, no readable words and no picture, about the same size as the original. A good cipher makes every byte look as likely as every other, so nothing about the content shows. What can still show is the outside: that the file exists, roughly how big it is, when it changed, and any name or label stored next to it in plain text.
On this page
Open one and look
Take a photo and open it in a hex viewer, a tool that shows a file’s raw bytes. Near the top you’ll find recognisable things: a format marker, the camera model, the date, maybe GPS numbers. Further down, the picture data has its own rhythms.
Now open the same photo after a vault has encrypted it. Every row looks the same: a jumble of values, none more common than another. No camera model. No date. No hint of a face or a page. If you counted each byte value across the file, the counts would come out almost flat.
That flatness is the point. A strong cipher, such as the AES modes NIST describes, makes its output impossible to tell from random data without the key.
Why it looks random
A cipher mixes every bit of the original with a key in a way that spreads any change across the whole result. Two photos that differ by one pixel come out completely different. The same photo encrypted twice, with a fresh random value each time, also comes out different. So there are no repeats for anyone to spot, and no way to guess what the bytes mean.
What still shows
Encryption guards the content. The outline around it often stays visible.
- That the file exists. A folder of encrypted files tells someone you keep encrypted files.
- Its size, roughly. A blob of several megabytes is more likely a photo than a note. A long video looks long.
- When it changed. File dates come from the system, not the cipher.
- A header. Many formats start with a short readable label and some settings, so the right app knows how to open it.
- Names stored beside it. If an app encrypts the photo but keeps “passport.jpg” in a plain database, the name tells the story the photo can’t.
That last point is the one to check in any app: are names, captions and notes encrypted too, or only the image?
Real encryption, or a renamed file?
Some apps “lock” files by moving them to a private folder and changing the extension. Open one in a hex viewer and you will see the photo’s normal header and readable metadata. That is not encryption. Signs of the real thing:
- No readable metadata anywhere in the file.
- No photo header at the top, only noise after any short format label.
- A changed byte breaks it. An authenticated mode refuses a file that was altered.
You can’t usually reach an app’s files on an iPhone without a computer and some care. The guide to how vault apps work explains what happens behind the screen instead, and the AES guide covers the cipher.
Copies count too
Encryption on the phone means little if the backup holds a plain copy. When a vault backs up, the files should leave the phone already encrypted, so the backup looks as noisy as the original. For what a phone backup holds in general, see what is in an iPhone backup.
Where Sealed helps, and where it doesn’t
It helps because each file is encrypted with its own key before it is saved. Sealed encrypts every file with AES-256-GCM before it is saved. Each file gets its own random 256-bit key, and that key is sealed with your vault key.
It helps with the text around a file, not only the file. Names, notes and the fields of a record are sealed with your vault key too, not just the photos.
It helps in the backup and the open copy, which hold the same noise. Files, names, notes and record fields are encrypted on your iPhone before they are uploaded, so iCloud receives only ciphertext. Each file in the open copy is the vault’s own encrypted file, copied byte for byte. The list of what the open copy holds is encrypted too, so the folder doesn’t even show how many items are in it.
It doesn’t keep the outline of a backup out of view: In your iCloud backup, Apple can see each record’s type, a random record name, when the record was created and changed, the size of its files and how many records there are, but not what is in them.
Questions and answers
Can I tell which app made an encrypted file?
Sometimes. Many formats start with a short fixed label, a few readable letters, so the app can recognise its own files. That label names the format, not the content.
Does an encrypted file get smaller, like a zip?
No. It stays about the same size, plus a little for the key data and the check at the end. Encrypted data also can’t be compressed afterwards, because it has no patterns left to squeeze.
If I change one byte, what happens?
With an authenticated mode the whole file is refused. Large files are encrypted in chunks, and Sealed refuses a file that has been changed, reordered or cut short.
Sources
What this page says about Sealed was checked against the app on .
- NIST, SP 800-38D, Galois/Counter Mode (GCM) and GMAC — published November 2007; GCM is authenticated encryption, so a changed file fails its tag. Read 13 Nov 2026
- Sealed on the App Store — the listing for the app used as the example
Get Sealed
Sealed is free to download, and Sealed Pro is an optional in-app purchase.