How to extract images from an FB2 without uploading it
Every "free" online FB2 tool you’ve used uploads your book to a company server, extracts it there, and — in several documented cases — keeps a copy or a live download link for days, or limits free users to a few conversions a month. For books you bought, were sent in confidence, or simply wouldn’t post publicly, that’s an unnecessary risk. The safer approach is to extract the file where it already is: on your own device.
This tool does exactly that. When you drop an FB2 here, your browser:
- Checks the file is really an FB2 book — by its magic bytes and its XML root, not its name — so a JPEG renamed .fb2 is refused with a clear message, a CBZ or plain .zip renamed .fb2 is refused with a pointer at the CBR tools, an EPUB renamed .fb2 is refused with a pointer at the Extract Images from EPUB tool, a PDF renamed .fb2 is refused with a pointer at the Extract Images from PDF tool, a DOCX renamed .fb2 is refused with a pointer at the Extract Images from DOCX tool, an XLSX renamed .fb2 is refused with a pointer at the Extract Images from XLSX tool, a legacy .doc is refused with instructions to convert it in Calibre first, and plain text is refused with an explanation instead of a cryptic error. A real FB2 saved with the wrong extension still extracts, and an FB2.ZIP — one FB2 book inside a ZIP — opens here too.
- Reads the book’s own images in document order — the <binary> elements are base64-decoded, the <image> references in the <coverpage> and <body> are followed in the order they appear, the cover comes first, and binaries never referenced by any <image> come last in binary order. Non-image binaries are listed as skipped, image references that point at a missing <binary> are listed as missing, and a book with no readable images is refused with a clear message instead of a cryptic error.
- Hands you the originals — download one image and it saves under its binary-id filename where the id gives one (cover.jpg), else image-01, image-02 and so on in document order; download the book as a ZIP and every image is renamed sequentially the same way. Nothing is re-encoded, rasterized or resized at any point: the bytes you download are the bytes that were stored in the book.
What makes this extractor different
Most pages that top the results for this search convert on a server, or handle one file at a time with no previews — instead of handing you the images themselves. The desktop options are installs, not browser tools. This page does the simpler job, and does it fully in the browser: no upload, no monthly cap, no account, no 10 MB limit, a batch of 20 books, document order with the cover first, binary-id filenames, per-book and combined ZIPs, and a live network-request counter so you can verify the privacy claim yourself.
Honest limitations
Verbatim means verbatim — no quality recovery
JPEG throws away detail when it compresses, and extracting cannot put it back. But nothing is lost either: the source bytes download unchanged, in every format. There is no quality setting because there is nothing to re-encode.
Metadata stays in the files
Extraction copies the stored bytes, so EXIF and other metadata inside each image is kept — including location data, if the image has any. The book’s own text and formatting are never touched, but the images themselves are untouched too. Strip metadata yourself before sharing an image publicly.
HEIC preview
HEIC images are extracted as-is, exactly as stored. Most browsers cannot display HEIC, so the page shows a note instead of a broken image in that case, with the format and size shown. The file itself still downloads byte-for-byte and opens in any viewer that supports the format.
Some FB2s embed only a cover
Many FB2 books carry a single picture — the cover — and no body illustrations at all. That is not a failure: the cover still extracts, and the card says how many images the book held. A book with no <binary> elements at all is refused with a clear message.
Missing image references
A book sometimes references an image id that has no matching <binary> element — the illustration was dropped when the book was made, or the reference is stale. This page lists it as missing on the book card, with the id named, instead of silently dropping it. The images that do exist still extract normally.
No text, linked images or FB2.ZIP bundles
This tool pulls out images only: it does not extract the book’s text, it does not download pictures linked from the web (only embedded images have bytes inside the file), and it opens one book per ZIP — an FB2.ZIP holding several books is refused, so unzip it and add the books one by one.
Document order, not binary order
Document order comes from the <image> references in the order they appear in the book — the coverpage image first, then body images in ref order. The order the <binary> elements sit in the file is not the reading order, so a picture stored late in the file can still be the first illustration in the text. Binaries never referenced by any <image> come last, in binary order.
Encodings and odd binaries
FB2 books arrive as UTF-8, UTF-16 or windows-1251, and this page reads the encoding from the XML declaration or the byte-order mark. A <binary> whose base64 is invalid means the book is corrupt and is refused; a binary that holds no picture (a font, a stylesheet) is listed as skipped. There is no encrypted-FB2 standard, so no protected-book handling is claimed.