Updated Nov 14, 2026
Bluesky exports your account as a single CAR file, which is a content-addressable archive in the IPLD format. That means your posts, likes, follows, blocks, lists and profile are all in there, signed by your DID, and the whole thing is the repo rather than a flattened dump of it. The catch is that the images and video you posted are not in the file. The records point at them by hash, and the actual files live on the CDN. You have to fetch them separately, and if the account is gone, so are they.
Bluesky is built on the AT Protocol, and the export reflects that. You get one file: a content-addressable archive, or CAR. It holds your entire repo, which is the same family of format as IPFS. Every record in it is signed by your DID, which means the file is a cryptographic snapshot of your account at the moment you clicked the button.
What is in there: every post you wrote, every repost, every like, every follow, every block, every list, your profile and your handle. What is not in there: the images and video attached to your posts. The records reference them by hash and nothing more. The actual media files live on the Bluesky CDN, and the CAR file does not include them.
There is a cap on how large a repo Bluesky will package into a CAR file. The export fails silently when you are above it. There is no error message, no partial download, no notification. The button just does not produce a file.
The usual way back under the cap is to delete old posts and bulk likes before requesting the export. If you have a large account, clean up first and then try again.
This is the part that catches people out. The CAR file holds records, and the records point at media by content hash. The images and video themselves are on the Bluesky CDN, and the export does not fetch them for you.
If the pictures matter, you need to grab them from the CDN while the account still exists. Once the account is deleted, the CDN references resolve to nothing, and the hashes in the CAR file become pointers to files that no longer exist anywhere.
There are tools that can walk the records in a CAR and download the referenced blobs. The @atcute/repo package on npm is open source and runs locally. Anything that reads a repo rather than just a list of posts will pair each record with its key, which is the part you want.
A CAR is a binary archive in the IPLD format. Your operating system will not recognise the extension and there is nothing useful that happens when you double-click it. That is normal rather than a sign the download failed.
To read it, use @atcute/repo from npm. It walks the records for you and pairs each one with its key. Do not hand the file to a random website to read for you. The CAR is enough to reconstruct your public record, and there are tools that run locally instead.
Because this is a repo and not a pile of documents, it is the one export on this site that another AT Protocol server could actually take, self-hosted ones included.
Export first, delete second. The ordering matters because the media on the CDN is tied to the account. Once the account is gone, the hashes in your CAR file point at nothing, and the pictures are gone for good.
There is no undo on a Bluesky deletion. The repo is removed, the handle is released, and the CDN references stop resolving. Take the copy while the account still exists.
If you want the short checklist instead of the full guide, use the service page.
A content-addressable archive, in the IPLD format. It holds your entire AT Protocol repo: posts, likes, follows, blocks, lists, profile and handle, all signed by your DID. It is the same family of format as IPFS.
No. The records in the CAR reference your images and video by content hash, but the actual files live on the Bluesky CDN. You have to fetch them separately, and they are only available while the account exists.
There is a repo size cap, and the export fails silently above it. Delete old posts and bulk likes to get under the cap, then try again.
Use @atcute/repo from npm. It is open source, runs locally, and walks the records for you. Do not upload the file to a website to read it. The CAR is enough to reconstruct your public record with local tools.
No. DMs belong to the other person as much as to you, and the CAR does not include them.
In principle, yes. The CAR is a full repo and another AT Protocol server could take it. In practice, there is a known open bug around re-creating record keys from an exported CAR, so importing can be fiddly.
No. It makes a copy and changes nothing about your account.
Last verified: Nov 14, 2026. Steps checked against bsky.app. Report an outdated step →