How to use FbZip2Blue

This guide describes the browser web app at /webv/: importing Meta (Facebook, Instagram, Threads) or X (Twitter) archive ZIPs, reviewing parsed posts, and (with a subscription) publishing to Bluesky.

What you need

• Account — Sign in with the identity provider configured for this site (for example Auth0). You must be signed in to create sessions and upload data.
• Archive export ZIP — A ZIP from one supported platform export flow (Facebook, Instagram, Threads, or X/Twitter). Very large exports are supported because uploads are sent in chunks.
• Bluesky (optional) — Only if you will publish: your handle (for example you.bsky.social) and an App Password from Bluesky (Settings → App passwords). Prefer a dedicated app password, not your main login password.

Supported platforms and export guides

• Facebook — Export guide: Download your Facebook information
• Instagram — Export guide: Access and download your Instagram information
• Threads — Export guide: Download your Threads information
• X (Twitter) — Export guide: How to download your X archive
• Destination publishing — Current publishing destination is Bluesky.

Main areas of the app

After opening /webv/, use the left navigation:

• Import & review (home) — Create the upload session, upload ZIPs, run the parse job, and optionally load a first page of posts in a compact table.
• Parsed posts — Full-screen review: paging, sorting, bulk edits, Bluesky controls, and per-post save/publish.
• Saved sessions — List all your uploads, open one again, go straight to parsed posts, delete a session, or purge old completed sessions.
• Language — Switch UI language (for example EN / FR / ES / PT) from the sidebar when available.

End-to-end workflow

1. Create an upload session

On Import & review, click Create upload session. The app assigns an upload ID (shown on screen). Everything you upload and parse is tied to this session until you create another one.

2. Session details (optional but recommended)

After metadata loads, you can set a session name, workflow status (Draft, Ready to post, Partially posted, Completed), and notes. Click Save session info to store these on the server. On the free plan, saving session details and editing posts may require a paid subscription—see the in-app notices.

3. Upload your Facebook ZIP(s)

Use Choose files to select one or more ZIP archives, then Upload selected ZIP files. A progress bar shows chunked upload progress. You can upload additional ZIPs to the same session if your export was split into multiple files.

4. Parse the archive

Click Queue parse job. A background worker extracts posts and media references from the archive. Use Refresh job or Wait until complete to follow progress. When the job finishes, the summary shows how many posts, images, and videos were detected.

If parsing fails, read the job message on screen; common causes are wrong file type, a corrupted ZIP, or an unsupported export layout. If you click Queue parse job while a job is already queued or running for this session, the app returns that existing job instead of starting a duplicate.

5. Review and edit posts

Open Parsed posts (or use Open dedicated posts page from home with your current session).

• Choose the upload — Pick a recent upload from the list and click Open, or open a session from Saved sessions (links include ?session=… for Import & review and /posts/{uploadId} for Parsed posts).
• Paging — Set page size (within allowed limits), use First/Previous/Next/Last, or jump to a post number. Turn on Included only to hide posts excluded from publishing.
• Per post — Edit text, set group selector (a label you can use for organization or filtering), toggle Include in upload, adjust hashtags via the picklist and/or quick-add field, then Save to persist changes (when your plan allows saving).
• Bluesky preview — Approximate appearance, a grapheme counter, and hints for long posts (hosted article, thread, or shorten). Open Preview for a larger modal with media and navigation.
• Public article — Optional per-row checkbox when your site requires it for hosted pages; otherwise long posts can use articles without extra marking.
• Sort — Click column headers where supported to sort by index, time, include flag, group, text, media counts, or posted status.

6. Bulk actions

On Parsed posts, use row checkboxes or Select all on page. Then you can:

• Apply bulk hashtags (add and/or remove) to all selected posts.
• Include or Exclude selected posts from the publishing set.
• Set a group selector for many posts at once (optionally only when empty).
• With publishing enabled: Bulk publish to Bluesky up to a capped number of selected posts per run, respecting credentials and dry-run settings.

From home (section 4), you can also apply a group selector across the current upload’s loaded page with similar “only empty” behavior.

Publishing to Bluesky (subscribers)

If your account has publishing enabled, the Parsed posts page shows a Bluesky card. Always test with Dry run first: no live post is created, but the app validates the flow and logs what would happen.

• Handle + App password — Enter your Bluesky handle and app password. These are sent to the server only for the publish request; use a dedicated app password and revoke it later if needed.
• Who can reply — After a real post is created, the app can set Bluesky’s reply audience (everyone, followers only, following only, mentioned users only, or nobody) using Bluesky’s thread gate rules.
• Force republish — When Dry run is off, live publishes are normally skipped for rows already marked posted; check Force republish only if you intentionally want to attempt posting again (use with care).
• Lists — Load lists fetches your Bluesky lists; you can assign a chosen list to selected posts (optional “only when group selector empty”). This helps downstream organization on Bluesky where supported.
• Long post publish mode — For text over ~300 graphemes: Auto, Short post only, Article + link, or Thread split (see section below).
• Single post — Publish on a row (or from the preview modal when available) publishes that post if it is included and credentials are valid.
• Publish log — Scroll the log for success, skip, and error lines; use Clear log when you want a fresh view. Long-post article publishes include an Article: URL line.

Posts marked Posted show a badge once a live publish succeeded for that row.

Long posts and publish modes (paid)

Bluesky feed posts are limited to about 300 graphemes. For longer imported text, use Long post publish mode on the Bluesky card:

• Auto — Hosted article + Bluesky link card when allowed; otherwise a Bluesky thread split.
• Short post only — Publish is blocked until you shorten the text.
• Article + link — Always uses a hosted article page plus teaser on Bluesky (paid; requires article publishing on your account).
• Thread split — Splits text into a reply chain on Bluesky; images on the first part only; no hosted article page.

Use Dry run first to confirm article URLs or thread behavior before going live.

Platform reliability and saved sessions

Sessions, parse jobs, and saved edits are stored on FbZip2Blue’s backend (PostgreSQL in production since 2026). Resume anytime from Saved sessions. After routine upgrades you should not need to re-import—if a session is missing, sign out and in, then contact support with your login email and session name (do not email or chat your ZIP file).

Free plan vs paid

The app may show an entitlement banner. Typically, the free plan lets you explore parsing and mark a limited number of posts as included, while saving session metadata, saving edits, bulk tools, deleting or purging sessions, and publishing require a paid subscription. Exact limits are shown in the product UI.

Saved sessions

Use Saved sessions to see every upload: names, workflow status, post counts, files, and last update. Import returns you to home with that session loaded; Review posts opens Parsed posts for that upload ID. You can delete one session or purge completed sessions older than a chosen number of days (when permitted).

Privacy and data

Your ZIP and parsed content are stored in the platform’s backend for your session so you can resume work. Do not upload archives you are not allowed to process. Remove sessions you no longer need, and use strong, unique app passwords for Bluesky.

Hosted article pages for long posts are reachable by URL (with an unguessable token). Use the per-row Public article checkbox when your operator requires explicit consent for public pages.

Troubleshooting

• 403 — Authentication or permission issue: sign out and sign in again; ensure your account is allowed to use the API.
• 413 — Request too large: reverse proxy or host upload limit may be smaller than your file; the server or proxy limit may need to be raised for multi-GB ZIPs.
• Failed to fetch — Browser could not reach the API (network, CORS, or offline). Retry; check VPN or firewall.
• Logout error — Logout or callback URL mismatch in identity configuration; contact the site operator.
• Parse job stuck or failed — Refresh job status; re-queue after fixing the ZIP; check that the export is a supported Meta or X archive format. If a job is already running, wait for it to finish before queueing again.
• Long post / 300 characters — Change Long post publish mode, use Thread split or Article + link, or shorten text; try Dry run and read the log.
• Bluesky publish errors — Verify handle/password, caps and 2FA (use app password), post length and media limits on Bluesky; read the publish log line for the specific error.
• Actions disabled — Often due to free plan restrictions or missing “Include in upload” / credentials / session save rights; read the yellow or gray notices on the page.

Quick checklist

1. Open /webv/ and sign in.
2. Create session → upload Facebook ZIP → queue parse → wait until complete.
3. Open Parsed posts, select your upload, review paging and filters.
4. Edit text, hashtags, group, include flag; save rows (if your plan allows).
5. Test Bluesky with Dry run, then publish (single or bulk) with reply audience as needed.
6. Use Saved sessions to resume later or clean up old data.

Open Web App FAQ