Higher DPI increases pixel dimensions and file size. Very large pages are scaled down so the canvas stays within browser limits.
Multi-page TIFF chains IFDs in file order—common for scans and archival packets.
Classic TIFF LZW (tag 5) is not emitted in-browser. “LZW” maps to PackBits RLE; “ZIP” uses Adobe Deflate (zlib)—both lossless relative to pixels.
When off, pages composite on white before rasterizing (typical for archival RGB TIFF).
Requires transparent PDF background. Off writes 8-bit RGB strips.
PDF parsing uses a PDF.js worker; TIFF packing may run in a Web Worker. Nothing is uploaded. Up to 10 PDFs, 100.00 MB each; up to 300 pages per document per run.
Vector PDFs rasterize at the chosen DPI—there is no “infinite” resolution. Encrypted PDFs must be unlocked first. BigTIFF, JPEG-in-TIFF, and some proprietary TIFF variants are out of scope for this encoder.
About this tool
Portable Document Format (PDF) became the universal packet for contracts, court filings, journal proofs, and internal memos because it preserves layout across operating systems—but many regulated workflows still insist on **Tagged Image File Format (TIFF)** masters. Archives, hospitals, insurers, and discovery vendors often standardize on multi-page TIFF stacks: each page is a high-resolution raster with explicit resolution tags, predictable compression, and a chain of Image File Directories (IFDs) that viewers traverse in order. Fax servers, legacy document imaging platforms, and some OCR ingestion queues were literally built around TIFF semantics, not PDF object streams. SynthQuery’s **PDF to TIFF Converter** closes that gap **in your browser**: you upload PDFs locally (nothing is sent to our servers for conversion), choose raster DPI, decide whether each source becomes **one multi-page TIFF** or **separate TIFF files per page**, and pick **uncompressed**, **PackBits** (TIFF compression tag 32773, labeled “LZW” in the menu to match common office vocabulary), or **ZIP / Adobe Deflate** (TIFF tag 8) for lossless strip compression. Optional **RGBA TIFF** is available when you enable a transparent PDF canvas and preserve alpha—otherwise the tool writes efficient **RGB** strips after compositing on white, which matches most print and archival briefs.
This introduction matters because teams routinely inherit PDF exports from modern suites but must hand TIFF to downstream systems that predate PDF-centric APIs. Legal discovery coordinators receive exhibits as PDF but must normalize to TIFF for Concordance-era tooling. Medical records clerks merge fax PDFs into lossless archives that PACS-adjacent scripts expect as .tif files. Government digitization grants sometimes specify TIFF bit-depth and compression families in the statement of work while contractors work entirely in Acrobat during layout. Rather than emailing files to opaque “free converter” sites, SynthQuery keeps rasterization and UTIF packaging on-device using **PDF.js** for parse and render, **Canvas** for pixel readback, and **UTIF.js** (with optional **Web Workers**) for baseline big-endian TIFF assembly—aligned with how our **PNG to TIFF**, **BMP to TIFF**, and **HEIC to TIFF** utilities already behave.
What this tool does
The hero workflow mirrors **PDF to PNG** so returning users recognize the mental model: a keyboard-focusable drop zone, hidden multi-file input filtered to PDF MIME types and extensions, a queue list with per-file removal, and honest caps—**ten PDFs**, **one hundred megabytes each**, **three hundred pages maximum per document per run**—to protect memory on consumer laptops and tablets.
**TIFF structure** is the differentiator. **One multi-page TIFF per PDF** walks the selected page range once, collects RGB or RGBA strips for every page, and emits a single filesystem object whose IFDs chain in order—ideal when a DAM, litigation support loader, or Hylas-style importer expects one attachment per matter volume. **One TIFF file per page** instead writes independent .tif files named with zero-padded page indices, which suits pipelines that ingest one raster per message or when you plan to feed pages into tools that do not read multi-page TIFF reliably.
**DPI presets** (72, 150, 300, 600) scale the PDF.js viewport relative to the PDF’s 72-unit inch convention, so pixel dimensions grow proportionally until an internal guard clamps extreme canvases. The chosen DPI also flows into TIFF **XResolution** and **YResolution** tags with inch units—critical metadata for print vendors even though it does not magically add detail that never existed in vector art or low-res scans embedded in the PDF.
**Compression** follows the same honest mapping as our other UTIF-based tools. **Uncompressed** (tag 1) maximizes decoder compatibility at the cost of the largest files—sometimes enormous for full-letter pages at 600 DPI. **PackBits** (32773) applies lossless run-length encoding to strip bytes; we label it **LZW** in the UI because many stakeholders use “LZW TIFF” colloquially for “lossless compressed TIFF,” even though classic TIFF LZW is technically tag 5 and is **not** emitted by this browser encoder. **ZIP / Deflate** (tag 8) wraps zlib-compressed strips and often wins on noisy gradients and photographic regions while staying lossless relative to decoded pixels.
**Transparency** is split into two toggles. **Transparent PDF background** tells PDF.js to render against a clear canvas instead of pre-filling white—useful for vector PDFs with knockouts. **Preserve alpha (RGBA TIFF)** only applies when transparency is on; otherwise the exporter flattens to **RGB** eight-bit samples per pixel. That pairing prevents accidental 40-megabyte RGBA masters when all you needed was opaque scans.
**Batch ergonomics** include **Download ZIP** when multiple TIFF outputs exist and **staggered multi-download** for browsers that block silent save storms. Thumbnails are **PNG data URLs** derived from the first rasterized page (or each page in per-file mode) because many browsers cannot preview arbitrary TIFF in `<img>` tags—so you still get visual confirmation without misrepresenting TIFF as a web-native format.
Technical details
**PDF** is a structured binary format combining page content streams, font resources, optional encryption, and embedded images. PDF.js interprets that structure, tessellates vector artwork into pixels, and paints into an HTML canvas at the computed viewport scale. **TIFF**, conversely, is a tagged container describing width, height, photometric interpretation, bits per sample, compression, and byte offsets to image strips. SynthQuery emits baseline **MM** (big-endian) TIFF with eight-bit samples, one strip per IFD (full image height), and **PhotometricInterpretation RGB** with optional **ExtraSamples** for unassociated alpha when you choose RGBA.
**Rasterization** means vector curves become pixels; anti-aliasing and transparency compositing happen during PDF.js render. **DPI** in this tool sets the mapping from PDF user units to pixel counts (72 PDF units nominally correspond to one inch at scale 1). Very large physical pages hit an internal canvas edge guard so browsers do not exhaust GPU memory—if you need extreme resolutions, split pages or use desktop specialist tools.
**Compression impact**: uncompressed strips are raw interleaved bytes; PackBits run-length-encodes those bytes; Deflate applies zlib to the same logical payload. None of these modes re-quantize color the way JPEG would—they are lossless relative to the raster PDF.js produced. **Embedded scans** inside a PDF cannot exceed their source resolution; upsampling DPI only enlarges pixels, not information.
Use cases
**Document archiving and long-term retention** teams often store TIFF because policies written in the 2000s explicitly name TIFF/G4 or RGB TIFF, while day-to-day authoring lives in PDF. Converting approved PDF exports to TIFF satisfies auditors without re-scanning paper.
**Legal discovery and exhibit preparation** frequently requires TIFF productions even when counsel receives PDF from opposing parties. Multi-page TIFF per volume preserves Bates-friendly ordering; per-page TIFF helps when a vendor’s uploader chokes on chained IFDs.
**Medical records and clinical workflows** sometimes bridge modern PDF portals with imaging backends that expect lossless TIFF frames. Browser-side conversion keeps PHI on the workstation when institutional policy forbids third-party upload converters—still follow your BAA and minimum-necessary rules for the finished files.
**Fax and unified-communications gateways** historically preferred TIFF handoffs. PDFs from email-to-fax services may need TIFF segments before entering legacy T.38 or store-and-forward queues that do not accept PDF directly.
**OCR preparation** pipelines occasionally request TIFF at specific DPI and compression families before recognition engines run. Rasterizing PDF text layers at 300 DPI often yields cleaner glyph edges than reusing aggressively compressed JPEG-in-PDF wrappers—though vector PDF text remains superior when the OCR engine accepts PDF natively.
**Print and prepress** shops may ask sales staff to deliver TIFF separations while clients only know how to export PDF from office suites. This tool gives account managers a browser tab instead of a weekend crash course in desktop publishing.
How SynthQuery compares
**Adobe Acrobat** and creative suites remain the reference when you need preflight, redaction, forms, or policy-driven PDF/A validation. **Desktop batch imagers** scale to watch folders, ICC profiles, and CMYK separations SynthQuery does not attempt in-browser. **SynthQuery** targets borrowed laptops, locked-down enterprise profiles, and mobile Safari sessions where installing software is impossible but a one-off TIFF production is due in an hour.
Compared with ad-supported “upload your PDF” converters, the differentiator is **privacy**: bytes stay in your tab. Compared with asking IT to run ImageMagick on a shared server, the differentiator is **accessibility**—no shell, no ticket queue, with explicit caps so expectations stay grounded. The following table summarizes positioning at a glance.
Aspect
SynthQuery
Typical alternatives
Privacy
PDF.js + Canvas + UTIF.js run locally; PDF contents are not uploaded for conversion.
Hosted converters may process files on shared infrastructure with unclear retention.
Multi-page TIFF
Optional single multi-page TIFF per source PDF with IFDs chained in page order.
Some free tools flatten to PNG or only emit one page unless you pay.
Compression clarity
Uncompressed, PackBits (32773), or Adobe Deflate (8) with FAQ on classic LZW tag 5.
Generic tools may mislabel compression or recompress without disclosure.
Single-purpose sites rarely sit beside AI writing, readability, and schema utilities.
Professional imaging depth
Baseline RGB(A) TIFF suitable for many archives; no CMYK, BigTIFF, or JPEG-in-TIFF write.
Acrobat and DAM transcoders offer ICC-aware CMYK and enterprise policy hooks.
How to use this tool effectively
**Step 1 — Confirm rights and policy.** PDFs may contain third-party fonts, watermarks, or confidential material. Ensure you may create derivative TIFF copies under your license, retention schedule, HIPAA role, or protective order before batching.
**Step 2 — Open synthquery.com/pdf-to-tiff.** The route lives in the public **Free tools** hub alongside other client-side converters; bookmark it if you routinely shuttle exhibits between PDF-centric and TIFF-centric systems.
**Step 3 — Add PDFs.** Drag files onto the dashed region or activate the file input (Enter/Space when the zone is focused). Only PDFs enter the queue; oversize files receive a toast with the exact byte cap. Remove stray files with per-row trash icons or clear the entire queue before a new job.
**Step 4 — Choose TIFF structure.** Pick **One multi-page TIFF per PDF** when your downstream tool expects a single attachment with ordered IFDs—common for archival manifests and some litigation loaders. Pick **One TIFF file per page** when you need loose rasters, per-page email attachments, or chained OCR microservices that watch folders for single-page drops.
**Step 5 — Select pages.** **All pages** exports the entire document within the three-hundred-page safety cap. **First page only** is a shortcut for cover sheets or representative thumbnails. **Specific pages** accepts comma lists and inclusive ranges (for example `1,3,5-8`) using the same one-based syntax legal teams already use when referencing Bates-stamped stacks.
**Step 6 — Set DPI.** Use **72** for screen references, **150** for light office print, **300** for many commercial specifications, and **600** when a vendor requests ultra-fine addressability. Remember: DPI scales pixels; it cannot recover sharpness from a bitmap scan that was blurry at capture.
**Step 7 — Choose compression.** Start with **ZIP / Deflate** when recipients run modern viewers (Photoshop, Affinity, Preview, many DAM transcoders). Fall back to **Uncompressed** when a validator rejects anything except tag 1. Choose **LZW (PackBits)** when you need modest lossless shrinkage with broad baseline TIFF support—read the helper copy for the tag-5 versus tag-32773 distinction.
**Step 8 — Transparency and alpha.** Leave both off for typical white-paper scans and print-first RGB masters. Enable **Transparent PDF background** plus **Preserve alpha** only when you truly need RGBA TIFF for soft masks or transparency-aware compositing.
**Step 9 — Convert and download.** Press **Convert to TIFF** and watch the status line: PDF.js loads each document, rasterizes each selected page, then the TIFF worker (or main-thread fallback) packs strips. Download individual cards, trigger **ZIP** for archives, or use staggered **Download all** if your browser guards multiple prompts.
**Step 10 — Post-process if needed.** For **JPEG** derivatives, SynthQuery does not ship a dedicated **PDF to JPG** route today—export **PDF to PNG** or use this TIFF output, then run **PNG to JPG** or **TIFF to JPG** depending on which container you produced. For **PDF packets** from TIFF masters, see **TIFF to PDF** when the flow reverses.
Limitations and best practices
Password-protected or certificate-encrypted PDFs must be unlocked before PDF.js can render. Extremely complex vector art may slow rasterization; reduce page count per run if the tab becomes sluggish. This encoder does **not** write BigTIFF, tiled TIFF, Fax Group 4, JPEG-in-TIFF, or GeoTIFF keys. Classic TIFF **LZW tag 5** is **not** emitted—use PackBits or Deflate instead, or re-save through desktop software if a contract literally mandates tag 5. For **PDF to JPG** specifically, use **PDF to PNG** or this tool plus **PNG to JPG** or **TIFF to JPG**. There is no **JPG to TIFF** page at SynthQuery today; **PNG to TIFF** after **JPG to PNG** is the practical lossless path. Always confirm color management with your print vendor—browser exports are sRGB-centric. Legally, TIFF conversion does not remove watermarks or classified markings; follow clearance procedures. For accessibility of derived images in web properties, add meaningful alt text in your CMS—the TIFF file itself does not carry HTML semantics.
Decode TIFF stacks back to PNG for browsers, slide decks, or social templates.
Frequently asked questions
Select **One multi-page TIFF per PDF** in the TIFF structure menu. The tool rasterizes each PDF page you include (via **All pages**, **First page only**, or **Specific pages**), encodes every page as its own IFD, and chains those IFDs in order inside a single `.tif` file on disk. That matches how many archival and litigation systems expect multi-page exhibits to behave. If you instead need loose files—one filesystem object per page—choose **One TIFF file per page**, which names outputs with zero-padded page indices derived from the PDF’s page numbers. When you queue multiple PDFs in one session, each PDF produces its own TIFF output (or set of per-page TIFFs) according to that structure choice; the tool does not merge unrelated PDFs into one TIFF automatically.
There is no universal number—archival quality means “enough pixels to represent the source content without wasting storage.” For born-digital vector PDFs, **300 DPI** is a common print reference; **600 DPI** helps when downstream vendors impose aggressive plate curves or when you anticipate zoom-heavy review. For PDFs that already contain scanned photos at modest resolution, higher DPI only upsamples soft pixels; prefer matching the embedded scan density or obtaining a fresh scan. **150 DPI** suits office reference copies; **72 DPI** is rarely appropriate for archival except screen captures. Remember SynthQuery writes resolution tags that describe the raster grid; they do not invent detail absent from the PDF.
Both options in this tool are **lossless** relative to the raster PDF.js produces before compression. **ZIP / Deflate** uses TIFF compression tag **8** (Adobe Deflate) with zlib, the same algorithm family PNG uses internally—often the best byte savings on gradients and photographic noise. **LZW** in the menu maps to **PackBits** run-length encoding (**TIFF tag 32773**), a historic Macintosh-style RLE that remains widely implemented. Classic TIFF **LZW tag 5** is **not** emitted by UTIF.js in this browser pipeline; if a contract literally requires tag 5, re-save through desktop software that licenses that encoder and verify decoder compatibility. **Uncompressed** (tag 1) stores raw strip bytes and maximizes compatibility at maximum file size.
No. Parsing, rasterization, and TIFF packaging run entirely inside your browser after the page loads. PDF.js fetches its worker script from your origin alongside the app; UTIF encoding may run in a dedicated Web Worker to avoid freezing the UI. Network traffic is limited to loading site assets—your document bytes are not transmitted to SynthQuery for this conversion. That architecture matters for confidential legal, medical, and financial PDFs, though you must still follow your organization’s policies about where finished TIFF files are stored, emailed, or synced to cloud drives.
Not directly. PDF.js cannot rasterize encrypted content without passwords and decryption keys. Unlock or export an unencrypted copy using the tool your policy permits—often desktop Acrobat or an approved enterprise PDF utility—then convert the unlocked PDF here. Attempting to bypass DRM or rights management may violate law or contract; always use authorized workflows.
Many browsers do not reliably decode arbitrary TIFF variants inside `<img>` elements, especially multi-page stacks. To give immediate visual feedback, the page generates a small **PNG data URL** thumbnail from the rasterized page while the UTIF encoder builds the true TIFF bytes. The downloaded `.tif` files are the authoritative output; previews are cosmetic stand-ins that do not affect TIFF compression or resolution metadata.
There is no dedicated **PDF to JPG** route today. Practical options: use **PDF to PNG** for lossless raster pages, then **PNG to JPG** with explicit quality control; or use this **PDF to TIFF** tool and run **TIFF to JPG** if your pipeline already prefers TIFF intermediates. JPEG is inherently lossy for photographic content; choose quality settings consciously when compliance requires readable fine print.
You may queue up to **ten** PDFs, each up to **one hundred megabytes**, similar to our **PDF to PNG** tool. Each document exports at most **three hundred** pages per run to protect memory on consumer hardware. Canvas dimensions are clamped if a page would exceed browser GPU limits—extremely large physical sizes may rasterize at a slightly lower effective scale than naive DPI math suggests. If conversion fails, try fewer pages, lower DPI, or split the PDF with an approved desktop tool first.
Leave both off for typical text-and-scan PDFs destined for print or fax systems that expect opaque white. Enable **Transparent PDF background** when the PDF uses knockouts or soft masks that should survive without a white matte. Enable **Preserve alpha (RGBA TIFF)** only when transparency is on and downstream compositing truly needs a fourth alpha channel—RGBA files are larger and some legacy readers ignore alpha. If you are unsure, prefer opaque RGB for maximum compatibility.
Acrobat and Creative Cloud tools offer calibrated color, preflight, batch actions, and enterprise deployment—capabilities a browser utility cannot replicate. SynthQuery instead delivers a **zero-install** path for baseline RGB(A) TIFF with honest compression tagging, explicit DPI metadata, and multi-page structuring choices. Use Acrobat when policies demand PDF/X, ICC profiles, or redaction; use SynthQuery when you need a fast TIFF packet on a machine where desktop software is blocked but modern Chromium or Firefox is allowed.