In a world without privacy, we create it.

Veldrinby CounterCustody
Download on the App StoreDownload on the App Store
Scan to download VELDRIN on the App Store.
TL;DRWant the short version? Click here.
The problem
Private files sit in a camera roll anyone can scroll, an album anyone can open, or a cloud you don't control.
The fix
Veldrin keeps them in a pattern-locked vault on your iPhone. No account, no vault list, and a red emergency button for when you're pressed to open it.
In short
What AES-256 is, what the 256 means, why the mode matters, and which questions an AES-256 claim on an app page leaves unanswered.

Why you need this

A strong cipher means little if the key is easy to reach. What you actually want is a vault where your private photos stay locked on your own phone, opened only by a pattern that you draw, with no account anyone can break into or reset. Veldrin keeps your files in an encrypted vault on the device, so the question of who holds the key has a short answer: you do.

Guide · 9 min read

AES-256 encryption explained: what it means for your data

AES-256 is a standard cipher that scrambles data using a 256-bit secret key, and the 256 describes only the length of that key. The cipher is rarely where encryption fails. The weak point is usually how the key is made, where it's kept and who can reach it, and an AES-256 label on an app page never tells you any of that.

What is AES, and what does the 256 refer to?

AES, the Advanced Encryption Standard, is a symmetric cipher, meaning the same secret key scrambles and unscrambles the data. NIST published it as FIPS 197 in 2001, and a 2023 update of that document made editorial changes without altering the algorithm. It works on blocks of 128 bits at a time and comes in three key lengths: 128, 192 and 256 bits. The number in AES-256 is the key length and nothing else, which is a smaller claim than the phrase tends to carry in an App Store listing.

How Veldrin applies it: the drawn pattern feeds a key derivation, and the resulting key encrypts the files.

Does a 256-bit key make your photos safer than a 128-bit key?

A longer key means more possible keys for an attacker to try. At 256 bits that space is far beyond what anyone can search by brute force, and the same is true, for practical purposes, at 128 bits. So the difference between AES-128 and AES-256 matters much less than the marketing suggests, and neither is the part that gets broken in real incidents. What gets broken is everything around the cipher:

  • A weak password or short PIN from which the key is derived, so an attacker guesses the password instead of the key.
  • A key stored next to the data it protects, such as in the same unprotected file.
  • A key held by a company that can be hacked, mismanaged or simply log in as you.
  • An app that encrypts on disk but leaves an unprotected copy in a cache, a thumbnail folder or a backup.

Think of the cipher as the lock on a safe and the rest of the system as the building around it. Nobody breaks into a bank by picking a good lock when the door beside it opens with a guessed code. The 256 tells you the lock is good. It says nothing about the door, the code, who has a spare key or whether the safe is bolted to the floor.

Why does the mode of operation matter as much as the key size?

A block cipher only handles 128 bits. A mode of operation says how to apply it to a whole photo or file, and the choice changes what an attacker can learn.

ECB (Electronic Codebook): don’t use

Electronic Codebook encrypts each block independently, so identical blocks of input produce identical blocks of output. In images that preserves visible patterns, and the outline of the picture survives the encryption. It's not a sensible choice for files.

The classic demonstration encrypts a bitmap picture in ECB mode and shows an image whose outline is still clearly visible, because large areas of one colour become large areas of one ciphertext. A photo is exactly the kind of data this hurts, and any current library that offers ECB as a default for files has made a poor default.

CBC and CTR: older and workable, with conditions

These chain or count blocks so patterns disappear. They hide content but don't by themselves detect tampering; someone who can alter the stored data may be able to change it without the app noticing, unless a separate integrity check exists.

CBC was the standard workhorse for years and remains in plenty of shipping apps. It's acceptable when it's paired with a separate integrity check, and a risk when it isn't, because some attacks against it work by feeding the decryptor tampered data and watching how it responds. Treat CBC in a new design as legacy, and ask what accompanies it.

GCM

Galois/Counter Mode, specified by NIST in SP 800-38D, gives you authenticated encryption: it hides the content and also lets the receiver detect modification. It depends on never reusing the same nonce with the same key, which is an implementation detail a user can't see and has to take on trust.

In practice GCM is a common default for encrypting files and records. Its one hard requirement, never repeating a nonce under the same key, is a discipline the developer carries and the user can't check, so the question to put to a vendor is how nonces are generated for each file.

What should you ask when an app says it uses AES-256?

Treat the phrase as the start of a question list.

Question to askWhy it matters
Where is the key made, and from what?A key derived from a four-digit PIN is only as strong as the PIN.
Who holds the key?If the company can unlock your files, so can anyone who compels or breaches the company.
What is encrypted?Photos, but also filenames, thumbnails, previews and metadata.
Is it tamper-evident?An authenticated mode detects altered files; a plain one may not.
What happens on recovery?If a reset can restore access, ask what that reset relies on.
Is there independent review?A claim nobody outside the company has checked is a claim and not evidence.

What an AES-256 line on a marketing page does not tell you

It doesn't tell you the mode, the key's origin, the key's owner, what else is encrypted beyond the file body, whether the backup is covered, whether thumbnails are covered, or whether anyone independent has looked. Every row of the table above is a question that line leaves open. A specific answer to each tells you something, and a repeated label tells you nothing.

How does a four-digit PIN defeat AES-256?

Suppose an app says it protects your files with AES-256 and unlocks with a four-digit PIN. There are only 10,000 possible PINs. If the key is derived from that PIN and an attacker can copy the encrypted file off the phone, they can try all 10,000 on their own computer in moments, with no lockout and no delay, and the cipher never had to be attacked. A well-designed app slows that guessing down by making each attempt expensive, or by tying the key to hardware the attacker can't copy; a poorly designed one does neither. The same file, the same cipher and the same label can mean very different things, and a long passphrase kept in your head or a password manager does more for your photos than any change to the key length.

Is AES-256 what protects photos on an iPhone and in iCloud?

iPhone photos are already encrypted on the device when the phone is locked, which is why the strength of your passcode matters. In iCloud, Apple's data security overview says standard protection encrypts data in transit and on the server but leaves Apple holding the keys for Photos, while the optional Advanced Data Protection moves Photos to end-to-end encryption. Both count as encrypted, and they differ in who can decrypt. The answer to is it encrypted is nearly always yes, while who can decrypt it, and how, is what separates products. We go further into it in our guides on iCloud photo encryption and end-to-end encryption for photos.

What does AES-256 mean for photo storage?

For a photo library, the cipher matters at three points: the file on the device, the copy in a backup, and the copy in transit or in the cloud. Apple's hardware keys protect the file on the device when the phone is locked, and a vault app adds a second layer under its own key. The backup needs its own check, since a vault that encrypts files on disk and then uploads plain copies to a backup has encrypted the wrong half. For the question of where each copy goes and who can open it, read about what lives in an iPhone backup.

Resolution is a smaller issue. Encryption doesn't touch image quality, because the file is restored bit for bit when decrypted. A vault that returns a smaller photo than the one you imported has recompressed it somewhere, which is an app decision and has nothing to do with the cipher.

Who uses AES-256 in practice?

AES is the symmetric cipher built into almost everything you use. iPhones and Macs use it in hardware for storage encryption, browsers use it for web traffic, password managers use it for their vaults, and disk-encryption tools use it everywhere. US government guidance approves it for protecting classified information, and the Committee on National Security Systems says TOP SECRET information requires 192-bit or 256-bit keys. Wide use is the strongest argument for it: a cipher with that much scrutiny and that many deployments has had its weaknesses searched for by a great many people. The trouble, as above, is the work around it.

Common misconceptions about AES-256

  • 256-bit means twice as strong as 128-bit. The search space is vastly larger, but both are beyond brute force today, so the practical gain is small.
  • Impressive labels on a listing mean something specific. Phrases about government or banking use are marketing words, not standards.
  • Encrypted means private from the company. Only if the company lacks the key, a point we take up in zero-knowledge encryption.
  • If it's open source or audited, it's safe. Review helps, but only for the version that was reviewed and the questions the reviewer was asked.
  • Quantum computers make AES obsolete. This is a debated, evolving topic. Check NIST's current post-quantum guidance, not a headline.

For the wider question of how to judge an app, see are photo vault apps safe.

What to take from an AES-256 label

Treat AES-256 as a good ingredient and ask about the recipe. It tells you the lock is sound, but the answers that decide whether your photos are private are where the key comes from, who can reach it, what else is encrypted, and what happens when you lose the unlock. Veldrin leaves cipher labels off its pages for that reason and states keys, limits and recovery instead; the security features page is the list to check any vault app against.

Questions people ask

What does AES-256 stand for?

AES is the Advanced Encryption Standard, a cipher published by NIST, and 256 is the length in bits of its secret key. The cipher itself works on 128-bit blocks regardless of key length.

Can AES-256 be cracked?

Guessing the key by brute force isn't realistic. Breaches usually come from weak passwords, poorly stored keys, bugs or company-held keys, and no cipher protects against those.

Is AES-256 better than AES-128?

It has a larger key, but both are far beyond brute force today. Implementation quality and key handling matter more than the number on the label.

Does AES-256 mean an app can't see my photos?

No. It only says a cipher is used. Whether the company can decrypt your photos depends on who holds the key and how it was made.

Is AES-256 quantum-resistant?

Largely, for symmetric encryption. A quantum computer running Grover's algorithm would roughly halve the effective key length, leaving AES-256 near a 128-bit level, which remains out of reach. The larger quantum risk falls on public-key cryptography, so check NIST's current guidance for details.

What is the difference between AES-128 and AES-256?

The key length, and with it the number of possible keys. Both are far beyond brute force today. AES-256 adds margin, and uses more rounds, but real-world breaches come from weak passwords, stored keys and backups, not from the choice between the two.

Is GCM better than CBC for photo storage?

Generally yes. GCM detects tampering as well as hiding content, whereas CBC needs a separate integrity check to do the same. Either can be implemented well or badly, so ask how the vendor handles nonces and integrity.

Sources

VELDRIN

Look past the cipher label and see how Veldrin handles keys, recovery and limits.

See Veldrin on the App Store