Initializing... drag & drop files here
Supports: ODP
People arrive at this conversion for one of two reasons: a print shop, journal or archive asked for TIFF specifically, or they assumed TIFF is simply "the high-quality one". The first reason is a good one and this page is exactly what you need. The second is worth a minute of your time, because TIFF is not automatically the sharpest option and, at this converter's default settings, it is not even the smallest — it is the format that gives you the most explicit control over how the pixels are stored. Short answer: convert an OpenDocument Presentation to TIFF when something downstream demands TIFF, and change the Compression Type before you do; otherwise PNG or PDF is usually the better slide export.
One 3308 × 1861 pixel render of the same text-and-headline slide, written out by each encoder at typical settings.
| Format | Lossless? | Size on that slide | Opens in a browser | Typical reason to choose it |
|---|---|---|---|---|
| TIFF, LZW compression | Yes | 79 KB | Safari only | A print, scanning or archive workflow that specifies TIFF |
| TIFF, JPEG compression (this page's default) | No | 382 KB | Safari only | Almost never — see below |
| PNG | Yes | 50 KB | Everywhere | Sharp slide rasters for the web, screenshots, line art |
| JPG, quality 95 | No | 280 KB | Everywhere | Photo-heavy slides where universal support matters |
| WebP, quality 95 | No | 40 KB | Everywhere except very old browsers | Small web images with good text fidelity |
| AVIF, quality 95 | No | 20 KB | Chrome 85+, Firefox 93+, Safari 16.4+, Edge 121+ | The smallest modern web image |
| Vector, not raster | n/a — one file for the deck | Everywhere | Keeping the whole deck as one document with real text |
The PNG, WebP and AVIF rows are the formats written at their own encoders' settings, not necessarily the defaults each xconvert page ships with. The row that surprises people is TIFF-with-JPEG. A slide is mostly flat colour and crisp lettering, which a dictionary coder such as LZW handles far better than a DCT-based codec does. So the lossy default here throws pixels away and produces a file almost five times larger than the lossless option.
.odp onto the page or click "+ Add Files". Queue as many decks as you like; they all convert with the same settings.Same slide render, same default quality preset, each Compression Type option measured.
| Compression Type | Lossless? | Size | Verdict for slides |
|---|---|---|---|
| ZSTD | Yes | 26 KB | Smallest lossless, but a modern extension older readers reject |
| WebP | No — lossless mode is not enabled here | 40 KB | Small, but do not use it if you asked for TIFF to avoid loss |
| DEFLATE | Yes | 56 KB | Excellent lossless choice, broadly supported |
| LZW | Yes | 79 KB | The safe default — every TIFF reader handles it |
| JPEG / LOSSY (duplicate entries) | No | 382 KB | Lossy and larger than the lossless options on slide content |
| PACKBITS | Yes | 5.3 MB | Only for very old software that supports nothing else |
| NONE | Yes | 18.5 MB | Only when a spec demands uncompressed data |
| CCITT Fax 4, JP2K | — | — | Both failed outright on a colour slide; do not select them |
Not inherently. Both can be pixel-for-pixel lossless, and when they are, the image data is identical — you cannot see a difference because there isn't one. On our test slide the lossless PNG was 50 KB and the lossless LZW TIFF was 79 KB, so PNG was both smaller and universally viewable. TIFF's advantage is not fidelity, it is control and metadata: you choose the compression scheme explicitly, and print and archival systems are built around its tag structure. If nothing downstream requires TIFF, PNG is the better slide raster.
No, not for slides. It opens on JPEG, which permanently discards pixel data even though the extension is still .tiff, and on our measurement it produced a 382 KB file where lossless LZW produced 79 KB. The only situation where JPEG compression makes sense is a slide that is essentially one full-bleed photograph, and even then you would usually be better served by an actual JPG file.
.tiff and .tif versions of this converter?Only the filename suffix — the file contents are the same format. This page writes .tiff; ODP to TIF writes .tif and goes deeper on the specification itself, including where the two spellings came from. Both pages also expose a "File extension" dropdown offering either spelling, with neither preselected, so you can override the choice after you have landed on one of them.
Not through this route. The Image Transparency control on this page is a colour fill, and it defaults to White, so any see-through area of a slide is painted solid before the TIFF is written. There is no "keep transparency" entry available for TIFF output here. If a transparent background is what you need, ODP to PNG is the conversion to use, since PNG carries an alpha channel and the transparency option behaves differently there.
One TIFF per slide. Multi-page TIFF is a real part of the format and scanners use it constantly, but this converter renders each slide independently and writes it as its own single-page file. A 30-slide deck therefore returns 30 files, with a "Download all (ZIP)" button in the results. If a single file for the whole deck is what you actually want, ODP to PDF is the right conversion.
300 DPI is the default and is the long-standing print standard; it is the right answer unless someone told you otherwise. Go to 600 DPI when a printer or archive spec asks for it, or when a slide carries footnote-sized type you need legible on paper. Above that the returns shrink quickly while the pixel count does not: the 1200 DPI setting turns a widescreen slide into roughly 98 megapixels, which is around 295 MB of raw pixel data per slide before compression.
Because a TIFF holds a single frame with no timeline. Entrance builds, motion paths, slide transitions and any embedded audio or video are dropped, and each slide is captured in the state it reaches after every build has finished playing. This is true of every still-image target, not just TIFF. Keep the original .odp and present from Impress if playback matters.
The deck is re-rendered from its shapes and text runs rather than screenshotted, so a font that is neither embedded in the .odp nor installed on the render machine gets substituted with the closest available match, which can shift line breaks and autofit text. Fix it at the source: in Impress choose File ▸ Properties ▸ Font and tick "Embed fonts in the document", then save and re-upload.
Your .odp is uploaded over an encrypted connection and rendered on our servers — this is a server-side conversion. The upload and the finished TIFF files are deleted automatically a few hours after conversion, no account is needed, the output carries no watermark, and your files are never shared or made public.