CBZ 轉 PDF

JPEG and PNG pages are copied into the PDF as they are, with no re-encoding, so the artwork looks exactly like the original and the file size stays about the same. Other formats such as WebP, GIF, or BMP are decoded and re-saved as lossless PNG before embedding.

Pages are sorted by filename using natural ordering, so page2.jpg comes before page10.jpg. Files in subfolders are included and sorted by their full path, and non-image files such as ComicInfo.xml are ignored.

Each page is sized to the pixel dimensions of its image, one point per pixel, so a double-page spread comes out as a wide landscape page and single pages stay portrait. There's no option to force one size here; if you need uniform pages, run the result through Fix Page Size.

.cbr archives are accepted and can be mixed with .cbz files in the same batch. CBR files are routed through the PyMuPDF engine, which downloads on first use, so they take a little longer than CBZ files, which are unpacked directly in the browser.

JPEG and PNG are embedded directly. GIF, BMP, WebP, AVIF, TIFF, HEIC, and JXL are converted to PNG by your browser first, so those less common formats only work if your browser can display them; TIFF, HEIC, and JXL fail in some browsers. The converter checks the actual image data rather than the extension, so a PNG named .jpg still works.

A single CBZ can hold up to 2,000 images, with each image capped at 100 MB and 500 MB of uncompressed image data per archive. Those limits keep the browser from running out of memory, and they're far above a typical comic issue.

Each archive becomes its own PDF named after the original file. One file downloads directly; two or more are bundled into comic-converted.zip.

No. CBZ archives are unzipped and rebuilt as PDFs entirely inside your browser, and CBR files are handled by an engine that also runs locally. Nothing from your collection leaves your device.