Everything you need to know about FbZip2Blue

A web platform to import Meta (Facebook, Instagram, Threads) and X (Twitter) archive ZIP files, then prepare content for Bluesky. It also builds searchable Messenger / WhatsApp chat archives from Facebook or WhatsApp exports.

A free desktop app and offline viewer for chat history. You pay once for the full converted archive (all conversations and media), not for the viewer. Build a preview or full ZIP at /webv/ or see the chat archive guide.

For posts → Bluesky, no — everything runs in the browser. For chat archives, the Windows desktop app is optional but recommended; download it free from the Chat Archive section in /webv/ or direct ZIP link.

Go to /webv/, sign in, choose your export ZIP, and click Upload and convert.

Yes. Multi-GB files are uploaded in chunks.

Yes. After conversion, use Download .fbzpkg on Parsed posts for an encrypted copy sealed to this browser profile, then re-open it under My packages (this device) in the same browser. Server copies are temporary — they may be purged after download or within 72 hours.

An encrypted package sealed to one browser profile (device-held keys). It holds parsed posts and media so you can resume in that same browser — not a portable file for another PC or browser. Use Download .fbzpkg after saving edits; open it from My packages (this device) in /webv/. See local conversion package guide.

No. The file only unlocks in the browser profile that downloaded it. Copying it to another machine, Chrome/Firefox/Edge profile, or phone will show a “different browser profile” error. Clearing site data for fbzip2blue.com also creates a new device key and blocks old packages. Keep working in the same browser, or re-download from an active server session if one is still available.

Yes — if you downloaded a .fbzpkg, keep that file and re-open it from My packages (this device) on the same browser profile. Temporary server staging is not the long-term store.

On Parsed posts, click Sign in with Bluesky when OAuth is enabled (recommended). That stores a short-lived session for publish without typing an app password. You can still use handle + app password as a fallback.

Not yet. Publishing today goes to Bluesky. Gander is shown as coming soon in the app until their ATProto OAuth is ready for third-party publish.

Yes, with a paid license. On Parsed posts, choose Long post publish mode: Auto (hosted article + Bluesky link when allowed, else thread), Article + link, Thread split on Bluesky only, or Short post only (you must shorten text).

For long posts, the full text can live on a page at fbzip2blue.com while Bluesky shows a short teaser and link card. The publish log lists the Article: URL after success.

Select rows on Parsed posts, then use Bulk text edit: find & replace, add to start, add to end, or remove text (optional case-sensitive find). Works on server sessions and local .fbzpkg packages.

Free — limited post preview and chat preview (1 conversation, 500 messages). Bluesky Standard (~$5) — full posts workflow + group invites, 1 Bluesky account. Chat Archive (~$69) — full chat download only (no Bluesky invites). FbZip Complete (~$89) — full chat + Agency posts + group invites (10 Bluesky accounts). Agency (~$30) — posts + invites, 10 accounts (no chat archive). Buy in /webv/; prices confirmed at Shopify checkout (CAD).

Yes — with a paid Bluesky licence (Standard, Agency, or Complete). In the free Chat Archive viewer, open a conversation and click Invite to Bluesky. Map archive names to @handles, then create a Bluesky group and/or send invite DMs. Private chat history is not republished. Chat Archive (~$69) alone does not include invites — see invite guide or FbZip Complete (~$89) for chats + invites + posts.

See parse troubleshooting. Do not email or chat your ZIP; use the job error text and conversion name.

Step-by-step articles live under /guides/, linked from Documentation — start with download your Facebook export, Facebook to Bluesky workflow, Messenger chat archive, or invite your group to Bluesky.

Sign in at /webv/ and open Feedback (beta). The product evolves quickly — we read every submission. For support (not research), use this FAQ, documentation, or contact email. Paid users can also use in-app support chat.