Initializing... drag & drop files here
Supports: ODT
PPM — Portable Pixmap — is the colour member of the Netpbm family, a deliberately primitive format that stores a tiny ASCII header followed by raw red, green and blue samples with no compression of any kind. Nobody chooses it for sharing; people choose it because an image-processing pipeline, a computer-vision toolchain, a raytracer or a university assignment wants pixels with nothing in the way. This page renders each page of an OpenDocument Text file into exactly that: a flat, uncompressed pixmap at the resolution you pick.
| Property | Value |
|---|---|
| Full name | Portable Pixmap |
| Family | Netpbm — PBM (bilevel), PGM (greyscale), PPM (colour), PNM/PAM (umbrella) |
| Origin | Jef Poskanzer's PBM format from the 1980s; PGM and PPM were added to the Pbmplus toolkit by the end of 1988 |
| Toolkit lineage | Pbmplus, final release 10 December 1991; replaced by Netpbm in 1993, still maintained |
| Magic number | P6 for the raw binary form written here; P3 for the plain ASCII variant |
| Header | Magic number, width, height and Maxval, all in ASCII decimal, then one whitespace byte |
| Sample size | 1 byte per sample when Maxval is under 256; 2 bytes per sample above it |
| Bytes per pixel | 3 at Maxval 255, 6 at Maxval 65535 — three channels either way |
| Compression | None. The specification itself calls the format "egregiously inefficient" |
| Transparency | Not supported — there is no alpha channel in the format |
| Colour space | ITU-R Recommendation BT.709 primaries with a gamma transfer function |
| Best for | Handing raw pixels to a program that would rather not decode anything |
| Property | Value |
|---|---|
| Full name | OpenDocument Text |
| Governed by | OASIS, then ISO/IEC JTC 1 |
| Standardisation | OASIS Standard 1 May 2005; adopted as ISO/IEC 26300:2006; v1.2 is ISO/IEC 26300-1:2015 |
| Latest version | ODF 1.4, approved as an OASIS Standard on 6 October 2025 |
| Physical structure | A ZIP archive of XML parts plus embedded media |
| Content model | Reflowable styled text, tables, fields, tracked changes, embedded images |
| Native applications | LibreOffice Writer, Apache OpenOffice Writer |
| Relationship to PPM | None whatsoever — one describes a document, the other describes a grid of samples |
Bit Depth sets the Maxval written into the PPM header, and Maxval is what decides both the file size and the number of distinct levels each colour channel can express. Because PPM is a three-channel format, the arithmetic is not the same as it would be for a bilevel PBM.
| Setting | Maxval written | Bytes per pixel | Distinct colours available |
|---|---|---|---|
| 16-bit (High Precision) | 65535 | 6 | ~281 trillion |
| 8-bit (Recommended, default) | 255 | 3 | 16.7 million |
| 1-bit (Black & White) | 1 | 3 | 8 |
The 8-bit and 16-bit settings behave exactly as you would expect: moving from 16-bit to 8-bit halves the file, because the sample size drops from two bytes to one. The 1-bit setting does not. The Netpbm specification says a sample occupies one byte whenever Maxval is below 256, and 1 is below 256, so each sample still takes a full byte — the file does not shrink. What changes is that every channel is quantised to two levels, which for three channels means eight possible colours: black, white, and the six saturated primaries and secondaries. The result is a posterised colour image, not the bilevel black-and-white page the label suggests. If you genuinely need a one-bit-per-pixel bitmap, the format for that is PBM, not PPM.
You can calculate it exactly, because nothing is compressed. An A4 page rendered at 300 DPI is about 2,480 × 3,500 pixels, which is roughly 8.7 million pixels; at three bytes per pixel that is about 26 MB per page, and about 52 MB per page at 16-bit. Drop to 150 DPI and the same page falls to roughly 6.5 MB, because halving the DPI quarters the pixel count. At 1200 DPI a single page passes 400 MB. Choose the lowest resolution your downstream tool will accept.
No, and this is the one genuinely surprising thing about this page. In our testing, the same rendered page written at the 8-bit setting came to 6,157 bytes and at the 1-bit setting to 6,155 bytes — a difference of two bytes, which is simply the header shrinking from "255" to "1". The pixel data is byte-for-byte the same length. If your goal is a smaller file, lower the Conversion Quality or use the Image resolution controls; bit depth below 8 will not help.
Several — one pixmap per page, numbered in page order. PPM has no multi-image container; each file holds exactly one raster. If you want the pages kept together in one file, that file cannot be a PPM. Convert the ODT to PDF instead, or render to images and assemble them afterwards.
Binary P6. The plain P3 variant writes every sample as decimal digits separated by whitespace, which roughly triples the size for no benefit other than being human-readable. Every Netpbm-aware reader handles P6, and it is what the conversion produces.
No. The format stores three samples per pixel and nothing else — the specification is explicit that it "allows very little information about the image besides basic color", with no alpha channel. That is why the Image Transparency control on this page offers colours rather than an "unchanged" option: the page has to be composited onto something before it is written, and it opens on White. If you need transparency, ODT to PNG is the route that supports it.
Because there is nothing for them to act on. Quality presets, target-file-size modes and compression levels all work by choosing how aggressively to encode; PPM has no encoder. The only levers that change the size of a PPM are pixel count and bytes per sample, which is why this page exposes Conversion Quality, Image resolution and Bit Depth and hides the rest.
Not much on a stock machine — browsers do not render PPM, and the image viewers that ship with Windows and macOS generally will not open it either. GIMP, ImageMagick, IrfanView, Netpbm's own tools, and essentially every scientific or computer-vision library read it happily. If you need something a colleague can double-click, convert onward with PPM to PNG or PPM to JPG rather than sending the pixmap.
None. PPM has no metadata fields at all, and the conversion strips what little the intermediate raster carried, so the file is a header and pixels. The characters, fonts, styles, comments and document properties from the ODT are gone the moment the page is rasterised — recovering the words requires OCR, and recovering the structure is not possible at all. Keep the ODT as the master copy.