Skip to content
pdfconversionapi

WPD to TIFF API

POST /v2/convert/wpd/to/tiff returns each page of a WordPerfect document as its own TIFF, stored without compression. The sample requests page 1 in black and white at 72 DPI and gets a single 612 × 792 file of 484,902 bytes with 72 DPI in its resolution tags.

Endpoint
POST /v2/convert/wpd/to/tiff
Accepts
wpd
Sample timing
0.543 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/wpd/to/tiff \
  -H "Authorization: Bearer $PDFCONVERSIONAPI_KEY" \
  -F File=@hearing-notice.wpd \
  --form-string PageRange=1 \
  --form-string ColorSpace=monochrome \
  --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.543 s median1 file, 474 KB
{
  "ConversionCost": 1,
  "ConversionTime": 0.543,
  "Files": [
    {
      "FileName": "hearing-notice-1.tiff",
      "FileExt": "tiff",
      "FileSize": 484902,
      "FileData": "SUkqAHhlBwBIAAAAAQAAAEgA…"
    }
  ]
}

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 hearing-notice-1.tiff, rendered by the API
Input
hearing-notice.wpd (1.8 KB)
Output
hearing-notice-1.tiff (474 KB)
Source
A two-page WordPerfect 5.1 public hearing notice for a fictional township, which we wrote byte by byte from the file format description (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
ImageResolutioninteger, default 150Resolution the page is drawn at, written into the XResolution and YResolution tags when you send it. Left out, pages are 1,275 × 1,650 and the tags carry no unit.Values: 36 to 600
ColorSpaceenum, default defaultmonochrome maps every pixel to 0 or 255 but still stores 8 bits per pixel, so at 72 DPI it is the same 484,902 bytes as gray. Left at default, pages are RGB, three bytes per pixel.Values: default, rgb, gray, monochrome
PageRangestringPages to return; the sample keeps page 1, and 2 returns hearing-notice-2.tiff alone.Values: Page numbers and ranges
MultiPageboolean, default falsetrue returns both pages in one LZW-compressed TIFF, hearing-notice.tiff: 242,358 bytes at the default 150 DPI, where each separate color page is 6,311,516 bytes. With ImageResolution=200 and ColorSpace=monochrome the 2-page file is 57,760 bytes, both pages one-channel.
ImageWidthintegerPixel width, with the height in Letter proportion: 850 gave 850 × 1,100 (935,198 bytes in black and white). No DPI is written unless ImageResolution is also sent.Values: 1 to 20,000
TransparentColorstringClears one exact color and adds an alpha channel; white at 72 DPI gave a 1,939,046-byte RGBA page with the paper transparent.Values: Color name, #RRGGBB or R,G,B
FileNamestringStem of the page files, hearing-notice-1.tiff and so on by default.
StoreFileboolean, default falseLinks to the stored TIFFs, kept for 3 hours, instead of the files in the response.

What carries over, and what doesn't

Kept

  • Letter proportions at the resolution you choose: 612 × 792 at 72 DPI, 1,700 × 2,200 at 200
  • Every pixel as drawn: pages are stored raw, or with lossless LZW in a multi-page file, so nothing blurs the 12 pt text
  • The DPI you send, in the resolution tags with inches as the unit
  • At 200 DPI in black and white, the struck-out date and the raised 'nd' stay legible

Lost or not yet supported

  • Compression, unless you send MultiPage=true: a single full-color page at the default 150 DPI is 6,311,516 bytes.
  • 1-bit storage. Black-and-white pages take a byte per pixel, eight times what a 1-bit TIFF of the same page needs before compression.
  • Thin strokes at low resolution in black and white: pixels are cut at middle gray, and at 72 DPI some letters of the sample's 12 pt text lose strokes, so 'final' reads as 'tinal'.

Limits

  • Page setup options such as PageSize return 400 "PageSize is not supported yet for WPD files"; pages keep the document's own size.
  • At most 2,000 pages per request, 16,000 pixels on a side and 100 million pixels per page; above that the API returns 413.
  • Requests up to 10 MB on the Free plan or 100 MB on paid plans, all files and fields together. Each conversion gets 120 seconds, then 504.

Where teams use it

Loading WordPerfect records into an imaging system

Records and document management systems built around scanned paper file pages as TIFF. Rendering old .wpd notices and letters to TIFF puts them next to the scans, one image per page.

Page images for OCR and redaction tools

Some OCR and redaction tools take page images and nothing else. ImageResolution=200 with ColorSpace=monochrome gives clean black-and-white pages of 1,700 × 2,200 pixels.

Questions

How do I get one multi-page TIFF?

Send MultiPage=true. For the sample this returns one 2-page TIFF of 242,358 bytes, LZW-compressed, where the default is two files of 6,311,516 bytes each. Converting to PDF with /v2/convert/wpd/to/pdf and sending that PDF to /v2/convert/pdf/to/tiff gave the same file byte for byte.

Why is each TIFF so large?

Single pages are written raw: width × height × bytes per pixel, plus a small header. MultiPage=true compresses them with LZW. A Letter page at 150 DPI is 1,275 × 1,650 pixels at 3 bytes each. Gray or black-and-white output stores 1 byte per pixel, and 72 DPI cuts the pixel count to under a quarter.

Which settings match a 200 DPI office scan?

ImageResolution=200 and ColorSpace=monochrome. Each page is then 1,700 × 2,200 black-and-white pixels with 200 DPI in its tags, 3,740,230 bytes uncompressed, or 57,760 bytes for both pages together with MultiPage=true.

Convert your first WPD file in a minute.