Skip to content
pdfconversionapi

PPTX to TIFF API

Post a deck to POST /v2/convert/pptx/to/tiff and you get one TIFF file with a frame for each visible slide. The sample, sent with ImageResolution=72, returns calloway-ferry-winter.tiff: five 720 × 405 frames in 176,483 bytes, tagged 72 DPI.

Endpoint
POST /v2/convert/pptx/to/tiff
Accepts
pptx
Sample timing
0.325 s median of 5 runsHow we measure
Request size
Up to 10 MB on the Free plan or 100 MB on paid plans, all files together

Request and response

Every sample below ran against the API before this page was published. Set PDFCONVERSIONAPI_KEY to your key and run it as is.

curl -sS -X POST \
  https://api.pdfconversionapi.com/v2/convert/pptx/to/tiff \
  -H "Authorization: Bearer $PDFCONVERSIONAPI_KEY" \
  -F File=@calloway-ferry-winter.pptx \
  --form-string ImageResolution=72 \
  -o response.json

# FileData is base64. Save the first file in converted/,
# or print the JSON error.
if jq -e '.Files' response.json > /dev/null; then
  mkdir -p converted
  name=$(jq -r '.Files[0].FileName' response.json)
  jq -r '.Files[0].FileData' response.json \
    | base64 --decode > "converted/$name"
else
  cat response.json
fi
200 OK0.325 s median1 file, 172 KB
{
  "ConversionCost": 1,
  "ConversionTime": 0.325,
  "Files": [
    {
      "FileName": "calloway-ferry-winter.tiff",
      "FileExt": "tiff",
      "FileSize": 176483,
      "FileData": "SUkqAFtwAABIAAAAAQAAAEgA…"
    }
  ]
}

Response from our test run on 2026-11-03. ConversionTime shows the median of 5 runs. FileData is shortened here; the real response carries the whole file as base64.

The sample, converted

The same file the code sends. Download the input and the output and compare them yourself.

First page of calloway-ferry-winter.tiff, rendered by the API
Input
calloway-ferry-winter.pptx (46 KB)
Output
calloway-ferry-winter.tiff (172 KB)
Source
A six-slide winter timetable deck for a fictional ferry operator, made by us for this site; slide 5 is hidden and slide 2 has speaker notes. (CC0-1.0). How it was made
Made by
2026-11-04, API build 9eeeb0640aba

Parameters

Send these as form fields next to the file. Names are case-insensitive. If you set one of the documented options below that we don't support yet, the request fails with a 400 that names it instead of returning a file made without it.

ParameterWhat it does
MultiPageboolean, default trueWith the default, every slide becomes a frame of one LZW-compressed TIFF. false returns -1.tiff to -5.tiff instead, and those single frames are stored uncompressed: 875,010 bytes each at 72 DPI, 3,793,742 at 150.
ImageResolutioninteger, default 150Pixels per inch; it is also written into the TIFF's resolution tags when you send it. At the default 150 the five frames are 1,500 × 843 and the file is 472,359 bytes, with a resolution tag of 1 and no unit.Values: 36–600
PageRangestringVisible slides to include. Two or more still make one multi-page file; a single slide comes back as its own uncompressed TIFF.Values: e.g. 1-3, 2,4
ConvertHiddenSlidesboolean, default falseAdd hidden slides as frames. The sample then has six frames, 197,231 bytes at 72 DPI.
ImageWidthintegerFrame width in pixels in place of a resolution; ImageHeight works the same way for the height.Values: 1–20000
ColorSpaceenum, default defaultAt 150 DPI, gray gave a one-channel 1,264,714-byte TIFF of slide 2 alone. In the multi-page file every frame keeps it: the five slides took 239,460 bytes in gray and 50,270 in monochrome, one channel each, against 472,359 in color, which rgb returns unchanged.Values: default, rgb, gray, monochrome
PasswordstringOpens an encrypted deck before its slides are drawn.
FileNamestringName for the result. A multi-page answer is <name>.tiff; with MultiPage=false each file gets the slide number after the name.

What carries over, and what doesn't

Kept

  • The slide order and the visible slides only, as frames 1 to 5 of one file
  • Lossless pixels with LZW compression in the multi-page file: 472,359 bytes for five 150 DPI slides, less than the five PNGs of the same slides (592,911 bytes)
  • The DPI you ask for, in the XResolution and YResolution tags of every frame
  • Slide backgrounds, fills, the chart and the picture as on the other image routes

Lost or not yet supported

  • Compression for single frames. A one-slide answer or MultiPage=false is stored raw: 3,793,742 bytes for one 150 DPI slide of the sample.
  • Speaker notes are not drawn, and detail stops at 200 pixels per inch: each slide, text included, is drawn as a picture at that density first, so a higher resolution only makes it bigger.

Limits

  • At most 2,000 slides per request (413 above that).
  • Each frame at most 16,000 pixels per side and 100 million pixels.
  • Requests up to 10 MB on the Free plan or 100 MB on paid plans; a conversion may take 120 seconds before the API returns 504.

Where teams use it

Filing decks in a records or document management system

If your records system was built for scanned paper and takes multi-page TIFF, one file per deck keeps the slides together, in order, with nothing that needs PowerPoint to open.

Sending slides into an imaging workflow

Imaging pipelines that page through TIFF frames can treat the deck like a scanned document. Pick a resolution with ImageResolution; it is recorded in each frame.

Questions

Why is a single-slide TIFF about eight times bigger than the whole deck?

Only multi-page files are LZW-compressed. PageRange=1 returns that slide uncompressed, 3,793,742 bytes at 150 DPI, while all five slides together are 472,359 bytes. Keep two or more slides in the file, or lower ImageResolution, if size matters.

How do I get one TIFF per slide?

Send MultiPage=false. The sample then returns calloway-ferry-winter-1.tiff to -5.tiff, uncompressed. If you need compressed single pages, take the multi-page file and split it in your own code.

What DPI does the TIFF say?

The one you send in ImageResolution, for example 72 in the sample. Without it the frames are drawn at 150 pixels per inch but the tags say 1 with no unit, so the file carries no usable print size.

Can I make a black-and-white TIFF of a deck?

Yes. ColorSpace=monochrome gives one-channel frames holding only black and white pixels, stored as 8 bits per pixel. In the multi-page file they are LZW-compressed: 17,436 bytes for the sample's five slides at 72 DPI. A single slide comes back uncompressed.

Convert your first PPTX file in a minute.