Brochure at print resolution
- Input
- sample.pub, 161,792 bytes, two A4 landscape pages, with {"dpi":300}.
- Output
- One 1,665,456-byte TIFF with two 3508 × 2481 frames tagged 300 DPI, in 1.2 s for the image step.
PUB → TIFF puts every page of the publication into a single lossless TIFF file, which is the shape many print shops and records systems still ask for.
From real runs
| Element | Result | What happens |
|---|---|---|
| Pages | Kept | All seven newsletter pages ended up as seven frames inside one TIFF rather than seven separate files, so the archive keeps one item per publication. |
| Image quality | Kept | Frames are stored with lossless Deflate compression, so there are none of the halos JPEG adds around small type. |
| Resolution tag | Kept | Each frame records its DPI: 144 by default, 300 when requested, so layout software places the page at its true printed size. |
| File size | Changed | Lossless pages are heavy: the two-page brochure was 1,074,064 bytes at 144 DPI and 1,665,456 bytes at 300 DPI, several times the PDF. |
| Searchable text | Lost | A TIFF holds pixels only; records systems that need full-text search should store the PDF alongside it. |
| Publisher layout faults | Changed | Any frame overflow or picture-over-text problem from the layout step is frozen into the TIFF, so check the frames before filing them. |
All seven newsletter pages ended up as seven frames inside one TIFF rather than seven separate files, so the archive keeps one item per publication.
Frames are stored with lossless Deflate compression, so there are none of the halos JPEG adds around small type.
Each frame records its DPI: 144 by default, 300 when requested, so layout software places the page at its true printed size.
Lossless pages are heavy: the two-page brochure was 1,074,064 bytes at 144 DPI and 1,665,456 bytes at 300 DPI, several times the PDF.
A TIFF holds pixels only; records systems that need full-text search should store the PDF alongside it.
Any frame overflow or picture-over-text problem from the layout step is frozen into the TIFF, so check the frames before filing them.
We converted our Microsoft Publisher sample (158 KB) with Office engine → Image engine on 2026-10-20. It took 2.4 s and produced a 1.0 MB TIFF file, 6.6× larger than the input. The engine raised 4 warnings, listed below.
Input · sample.pub · 158 KB
OLE2 compound document (legacy Office binary)
Output · sample.tif · 1.0 MB
1684 × 1191 px, deflate
LibreOffice and pdftoppm
soffice --headless --convert-to pdf issue.pub && pdftoppm -tiff -tiffcompression deflate -r 300 issue.pdf pagepdftoppm writes one TIFF per page; combine them with tiffcp if your archive expects a single multi-page file.
The HTTP API and the MCP server run the exact engine this page uses (Office engine → Image engine); the response carries the same warnings the web converter shows. Check support first with GET /api/v1/pairs?from=pub&to=tiff.
curl -X POST https://filetypeconverters.com/api/v1/convert \
-H "Authorization: Bearer $FTC_API_KEY" \
-F "file=@input.pub" -F "from=pub" -F "to=tiff" \
--output output.tifOne file. Every page becomes a frame inside the same multi-page TIFF, in page order; most image viewers show a page counter for it.
Only if your records system requires it. TIFF keeps an exact picture of each page but no text, while a PDF keeps the text searchable at a fraction of the size.
Usually 300 at the final printed size. Set dpi to 300; the file is tagged with it, so the shop's software sizes the page correctly.