Owner safety guide

Recover a wallet.aes.json backup from Blockchain.info

An intact wallet.aes.json backup may be recoverable when the legitimate owner remembers useful password characteristics or candidate passwords. The wallet identifier alone is not sufficient, and recovery is never guaranteed.

Still have the encrypted wallet.aes.json backup? Request a free, non-sensitive feasibility assessment →

How do you recover a wallet.aes.json backup?

There is no password-reset link or universal decryption shortcut. A realistic owner-authorized recovery path starts by preserving the original encrypted JSON, identifying its Blockchain.info era and format, checking that the backup is intact, and defining a bounded set of password candidates from the owner's memories. If the file is damaged or the password is strong and completely unknown, recovery may not be feasible.

Preserve the original context

Make read-only copies of the original backup and record its filename, creation date, source device, wallet era, and any wallet identifier you still have. Retain old emails and application records, but redact secrets before sharing screenshots.

Record memories descriptively

Useful clues include approximate password length, possible components, character substitutions, capitalization patterns, languages, separators, and passwords used around the same period. Do not put actual passwords or recovery phrases in the initial assessment.

Why attempts fail

The backup may be incomplete, from another wallet, damaged, or encrypted with a strong password outside the plausible candidate space. Format versions can also matter. A credible provider screens these facts before proposing work and never guarantees success.

Use a staged process

Start with non-sensitive facts and ownership evidence. If the case appears technically plausible, agree scope, fee terms, handling safeguards, and a private transfer method before any encrypted wallet artifact changes hands.

Open-source technical background: BTCRecover.

What the backup can—and cannot—prove

A valid encrypted backup is meaningful recovery material, but it does not by itself prove that the expected addresses or balance are inside it. Historical Blockchain.info formats also changed over time. Identification, integrity checks, and password-version details should come before any intensive attempt.

Fees and realistic expectations

KeyBack begins with a free, non-sensitive feasibility assessment. If the backup and remembered password information support a bounded recovery path, any success-fee arrangement is defined in writing before work. There is no guarantee, and a strong unknown password may remain impractical.

Avoid legacy-wallet scams

Do not upload the JSON to a “balance checker,” send it to an unsolicited helper, or pay a supposed blockchain tax. A legitimate recovery process cannot reverse transactions and should never ask for a seed phrase, private key, full password, or wallet file in the first message.

Frequently asked questions

Can a wallet.aes.json backup be opened without its password?

There is no universal bypass. A recovery attempt depends on the backup format, its integrity, and a realistic candidate space based on the owner's memories.

Is the wallet identifier enough?

No. An identifier or public address can help confirm context, but it does not decrypt the backup or recreate private keys.