Initializing... drag & drop files here
Supports: PUB
TIFF is what print shops, archives and document-management systems ask for when they want a Publisher page as a fixed, high-resolution raster rather than a live layout. This converter reads the .pub with LibreOffice's Draw component (the libmspub importer from the Document Liberation Project), renders each page at 300 DPI, and writes the result as TIFF.
The single setting worth changing is Compression Type. It defaults to JPEG, which is lossy — and on a Publisher page, which is mostly flat colour, rules and text, JPEG is also the worst choice for file size. LZW is lossless and typically several times smaller on the same page.
.pub onto the page or click "+ Add Files". Each file is handled as its own job, so a queue of publications will not be merged..tif and .tiff (identical bytes, different name). "Image resolution" defaults to "Keep original", which preserves the full 300 DPI render — use a Preset or Width x Height only if you deliberately want a smaller raster.Measured on a single A4 Publisher page rendered through this pipeline at 300 DPI (2481 × 3508 pixels, RGB), with the default "Very High" quality preset:
| Compression Type | Output size | Lossless? | Verdict |
|---|---|---|---|
| LZW | ~138 KB | Yes | Best all-round choice — lossless and universally readable |
| DEFLATE | ~124 KB | Yes | Slightly smaller than LZW; wide but not universal reader support |
| ZSTD | ~54 KB | Yes | Smallest lossless result, but needs a recent libtiff-based reader |
| WebP | ~61 KB | No | Lossy at the default preset; niche reader support inside TIFF |
| JPEG (the default) | ~566 KB | No | Lossy and four times larger than LZW on this kind of page |
| LOSSY | same as JPEG | No | Duplicate label — it maps to the same JPEG codec |
| PACKBITS | ~475 KB | Yes | Simple run-length coding; only worth it for legacy readers |
| NONE | ~26 MB | Yes | Uncompressed. Correct but impractical at print resolution |
| CCITT Fax 4 | — | — | Do not use. Bilevel-only; errors out on a colour page |
| JP2K (JPEG 2000) | — | — | Do not use. Not implemented for scanline writing |
JPEG's DCT is tuned for photographs. A Publisher page is text, rules, logos and large areas of one colour — exactly the content LZW's dictionary coding handles well and DCT handles badly, which is why the lossless option comes out smaller here. If your publication is a full-bleed photo poster, that ordering can invert; check both.
CCITT Fax 4 and JP2K deserve a specific warning: both fail during the write, but a TIFF header has already been emitted by then, so you can be handed a small file that looks like a real TIFF, reports the correct pixel dimensions, and contains no image data at all. Never pick either for a colour Publisher page.
| Property | Value |
|---|---|
| Source reader | LibreOffice Draw via libmspub |
| Intermediate | PDF, then a PNG render per page |
| Render resolution | 300 DPI (an A4 page becomes 2481 × 3508 pixels) |
| Colour | 8-bit RGB |
| Pages | One TIFF file per publication page — not a multi-page TIFF |
| Multi-page delivery | ZIP archive of the individual TIFFs |
| Default Compression Type | JPEG (lossy) |
| Default Image resolution | Keep original |
The one-file-per-page behaviour matters if a downstream system expects a single multi-page TIFF. This converter does not produce one; if you need pages bundled together, convert to PDF instead, which keeps everything in one document.
Because a Publisher page is not a photograph. JPEG splits the image into 8×8 blocks and codes frequency coefficients, which is efficient on continuous-tone detail and inefficient on sharp black-on-white text and large flat fills — the block edges themselves become expensive to encode at a high quality setting. LZW compresses repeated pixel runs, which is exactly what a page of text and flat colour is made of. On the A4 page measured above, LZW came out at roughly a quarter the size of JPEG and lost nothing.
They are the same format; only the filename differs. .tif survives from the DOS three-character extension era and is still the more common spelling in print workflows and on Windows. Pick whichever the receiving system expects — the file bytes are byte-for-byte identical either way.
No. The page is rendered to an opaque 8-bit RGB raster before the TIFF is written, so anything transparent in the layout is composited against the page background first. TIFF can technically carry an alpha channel, but this pipeline does not produce one — if you need real transparency, convert to PNG instead.
Not from this converter. Each rendered page is written as its own TIFF and multi-page publications come back as a ZIP. Multi-page TIFF is supported by the format but is not what this pipeline emits. If the goal is one file containing every page, Publisher to PDF is the right target.
300 DPI, fixed. That is the standard print-quality figure and it makes an A4 page 2481 × 3508 pixels and a US Letter page 2550 × 3300. There is no DPI selector on this page; the "Image resolution" controls resize the finished raster rather than changing the render resolution, so downscaling loses detail that a lower-DPI render would simply never have created.
CCITT Group 4 is a bilevel fax codec — it requires one bit per sample, so an 8-bit RGB page cannot be encoded and libtiff refuses. JP2K is registered as a TIFF compression tag but scanline writing for it is not implemented. In both cases the TIFF header (including the correct image width and height) is written before the encoder fails, leaving a few hundred bytes of valid-looking header with no image data behind it. Use LZW.
For a page image, yes: uncompressed or LZW TIFF is a long-established preservation format with no dependency on font availability. For a document, PDF is usually better, because it keeps the text as text — searchable, selectable, and a fraction of the size. Many archives keep both: PDF as the access copy, LZW TIFF as the preservation master.
It is uploaded over an encrypted connection, processed on our servers, and deleted automatically after a few hours — never shared and never made public. No account is needed and nothing is watermarked. If you want to shrink an existing set of TIFFs afterwards, our TIFF compressor works on the finished files.