Logo
Home Products Support Contact About Us


Split TIFF via Command Line — Server Batch TIFF Splitter

You have folders of multi-page TIFF files — faxes, scanned books, document archives — and a downstream system that expects single-page input. Opening each TIFF in an image viewer and exporting pages one at a time does not scale past two or three files. TIFF Paging X splits multi-page TIFFs into single-page TIFFs from the command line, in batch, with no GUI and no image-editor installation required. Install it on a Windows server, call it from a script or via ActiveX, and let it run unattended.

What TIFF Paging X Does

  • Batch splitting — pass a wildcard (*.tif) and the splitter processes every multi-page TIFF in one run
  • Page-range subsets — extract specific pages or ranges (-Pages 1-5,10-15) instead of every page
  • Custom file naming — control output names with patterns like {name}_p{page:000} to produce scan_p001.tif, scan_p002.tif, etc.
  • Compression preserved — output pages keep the source compression (CCITT G4, LZW, JPEG, ZIP, none) by default
  • Multi-page detection — single-page TIFFs in the input folder are skipped, not duplicated
  • No GUI — runs silently from the command line with no pop-up windows or confirmation dialogs
  • ActiveX / COM — call the splitter from .NET, VBScript, PHP, Python, or any COM-compatible environment to embed splitting into your own application
  • .bat scripting — save commands in batch files and schedule them with Windows Task Scheduler for fully automated splitting

Split TIFF command line

Download Free Trial

(30 days, no email)

Buy License

(server license, perpetual)

Windows 7/8/10/11 • Server 2008/2012/2016/2019/2022

Multi-Page vs Single-Page TIFF: Why Split?

Multi-page TIFF packs every page of a document into one file. Faxes, scanned books, and archived correspondence often arrive in this form because it keeps related pages together. The trade-off is that opening page 47 of a 200-page TIFF means decoding the entire stack to reach the right offset. Storage tools that index by file cannot reach individual pages. Distributed processing pipelines have to deserialize the whole file on every worker.

Single-page TIFFs store one page per file. Each page becomes addressable by file name. Document-management systems can attach metadata, Bates numbers, and OCR text to a specific page. Worker processes can pick up files in parallel without lock contention. Failed conversions affect one page, not the entire batch. When a multi-page TIFF needs to enter that workflow, it has to be split first.

Multi-page TIFFSingle-page TIFFs
Random accessDecode whole file to reach a pageDirect file open by name
Per-page workflowHard — index by page offsetTrivial — index by file name
Per-file sizeLarge (sum of all pages)Small (one page each)
Parallel processingLock contention on one fileOne file per worker, no contention
OCR pipelinesPre-split requiredFeed pages directly

How to Split TIFF Files from the Command Line

Step 1. Install TIFF Paging X

Download the installer from the link above and run it on your Windows server or workstation. The setup takes under a minute. No image editor, Photoshop, or imaging SDK is required — the splitter uses its own TIFF parser that handles CCITT G4, LZW, JPEG-in-TIFF, ZIP, and uncompressed pages.

Step 2. Open the Command Prompt

Open cmd.exe or PowerShell. The splitter executable is TIFFPaging.exe, located in the installation folder (typically C:\Program Files\CoolUtils\TiffPagingX\). Add it to your system PATH or use the full path in your commands.

Step 3. Run the Basic Split

The simplest command splits every multi-page TIFF in a folder:

TIFFPaging.exe C:\Scans\*.tif C:\Output\ -Split

This processes each .tif file in C:\Scans\ and writes one single-page TIFF per source page to C:\Output\. A 50-page invoice.tif becomes invoice_001.tif through invoice_050.tif. Single-page TIFFs in the input folder are skipped automatically.

Step 4. Add Naming and Range Options

Control the output with additional flags:

TIFFPaging.exe C:\Scans\*.tif C:\Output\ -Split -NamePattern "{name}_p{page:000}" -Pages 1-5,10-15 -log C:\Logs\split.log
  • -NamePattern "{name}_p{page:000}" — format output names; {name} is the source base name, {page:000} is the zero-padded page number
  • -Pages 1-5,10-15 — extract only pages 1 to 5 and 10 to 15; omit to split every page
  • -Compression Source — preserve source compression (default); use CCITTG4, LZW, or None to recompress
  • -log C:\Logs\split.log — write a per-file log for verification

Step 5. Automate with a .bat File

Save your command in a .bat file and schedule it with Windows Task Scheduler:

@echo off
"C:\Program Files\CoolUtils\TiffPagingX\TIFFPaging.exe" C:\Incoming\*.tif C:\Archive\Pages\ -Split -NamePattern "{name}_p{page:000}" -log C:\Logs\split.log

This runs the split every night (or at whatever interval you set) and writes a log file so you can verify the results. Pair it with a clean-up step that moves processed source files to an archive folder.

ActiveX / COM Integration

TIFF Paging X includes a full ActiveX interface. You can call the splitter from any COM-compatible environment — .NET, VBScript, PHP, Python, Ruby, or ASP. This lets you embed TIFF splitting into your own document-management application, intake portal, or imaging workflow without shelling out to a command-line process.

Example (C#/.NET):

TIFFPagingX Tpx = new TIFFPagingX();
Tpx.Convert("C:\\Scans\\book.tif", "C:\\Output\\", "-Split -NamePattern \"{name}_p{page:000}\" -log c:\\Logs\\split.log");

Example (PHP):

$t = new COM("TIFFPaging.TIFFPagingX");
$t->convert("C:\\Scans\\book.tif", "C:\\Output\\", "-Split -NamePattern \"{name}_p{page:000}\" -log c:\\Logs\\split.log");

The same call works from ASP.NET, VBScript, Python, Ruby, Perl, and JavaScript (Windows Script Host). Your intake application can accept uploaded multi-page TIFFs and return a directory of single-page files to the user in real time.

Online Splitters vs TIFF Paging X

FeatureOnline SplittersTIFF Paging X
Batch processingOne file at a timeUnlimited files per batch
File privacyFiles uploaded to third-party serverFiles never leave your machine
File-size limitTypically 50–100 MB capNo cap — gigabyte TIFFs supported
Compression preservedOften re-encoded to JPEGSource compression preserved
Page-range subsetsRareBuilt-in -Pages flag
AutomationManual onlyCommand line, .bat, Task Scheduler, ActiveX
Server deploymentNot possibleDesigned for servers, no GUI needed
Requires internetYesNo

When You Need TIFF Split Command-Line Conversion

  • Fax archives stored as multi-page TIFF. An inbound fax server writes each transmission as one TIFF with all pages stacked. The retention policy requires per-page archive entries with their own metadata. A nightly split job turns last-day's faxes into per-page files keyed by transmission ID and page number.
  • Scanned legal documents needing Bates numbering. A litigation support team receives a 1,200-page scan as a single TIFF. Each page needs its own Bates stamp and exhibit number. Splitting the TIFF first lets the Bates tool process each page as an independent file.
  • Per-page OCR pipelines. An archival imaging workflow feeds each page through OCR separately so failures can be retried per page. The OCR engine takes single-page TIFFs as input. The splitter sits in front of OCR and feeds it the right unit of work.
  • Tile-rendering and viewer back-ends. A document viewer renders one page at a time as the user scrolls. The back-end stores pages as individual TIFFs and serves them on demand. Multi-page TIFFs from intake are split on the way in, not on every viewer request.
  • Distributed processing. A document-classification service runs on a worker pool. Multi-page TIFFs cause lock contention because every worker needs the same file. Splitting on intake lets each worker pick up an independent page.

Why TIFF Paging X

Compression Preserved by Default

The splitter writes single-page TIFFs with the same compression as the source. CCITT G4 fax pages stay as CCITT G4. LZW-compressed scans stay as LZW. JPEG-in-TIFF photos stay as JPEG. No re-encoding, no quality loss, no surprise file-size growth. Override with -Compression only when you actually need to change the encoding.

True Server Application

TIFF Paging X is designed for unattended use. No GUI windows, no dialog boxes, no confirmation prompts. It runs silently from the command line or as part of a service — exactly what a production intake server needs. The same binary handles a five-page invoice and a 3,000-page archive scan.

Multi-Page Detection

The splitter inspects each input file before processing. Single-page TIFFs are skipped, not copied or renamed. This means you can point it at a mixed folder of single-page and multi-page TIFFs without producing duplicates or polluting the output. The log records what was split and what was skipped.

Pairs with TIFF Combine X

The opposite operation — combining many single-page TIFFs into one multi-page file — is handled by TIFF Combine X. The two tools share command-line conventions, so a workflow that splits on intake and recombines for archival storage uses one consistent syntax across both directions.

Download Free Trial

(30 days, no email or credit card)

Buy License

(server license, perpetual)

Windows 7/8/10/11 • Server 2008/2012/2016/2019/2022


quote

Tiff Paging X Customer Reviews 2026

Rate It
Rated 4.7/5 based on customer reviews
5 Star

"Our scanners write 200-page batches as single multi-page TIFFs, but our patient-record system stores one page per file with chart-specific metadata. TIFF Paging X runs as a Task Scheduler job every fifteen minutes against the intake folder. CCITT G4 compression is preserved exactly, which matters because we are bound by retention rules that disallow re-encoding source pages. Replaced an aging in-house tool that was breaking on TIFFs over 300 pages."

5 Star Margarethe Voss Document Imaging Specialist, Regional Health Network

"We digitize bound volumes as multi-page TIFFs and then need single-page files for the IIIF tile server. The splitter handles 800-page books without trouble, and the NamePattern flag lets us match the file names our viewer back-end expects. Page-range support is useful when a page needs rescanning — we just split the corrected range over the existing files. No GUI is exactly what we wanted on the back-end server."

5 Star Daniel Okafor Archive Manager, University Special Collections

"Production sets arrive as multi-page TIFFs that we have to split before our Bates-stamping tool can touch them. We integrated the ActiveX interface into our intake script so the split happens immediately on upload. COM call is straightforward and the splitter is fast enough for real-time response on a four-core box. Documentation could be more detailed on the NamePattern token list, but support answered our questions within a day."

4 Star Patricia Lindgren Litigation Support Lead

FAQ ▼

The basic command is: TIFFPaging.exe C:\Scans\*.tif C:\Output\ -Split. This processes every multi-page TIFF in the source folder and writes one single-page TIFF per source page. Add flags like -NamePattern, -Pages, or -log to control the output.
Use the -Pages flag with comma-separated page numbers and ranges. For example, -Pages 1-5,10-15,20 extracts pages 1 through 5, pages 10 through 15, and page 20 only. Pages outside the range are skipped, so the output folder contains only the pages you asked for.
Yes. The -NamePattern flag accepts a template such as "{name}_p{page:000}". {name} is the source base name, {page} is the page number, and {page:000} zero-pads to three digits. A 50-page invoice.tif becomes invoice_p001.tif through invoice_p050.tif.
Yes by default. CCITT G4 fax pages stay CCITT G4, LZW-compressed scans stay LZW, JPEG-in-TIFF photos stay JPEG. No re-encoding and no quality loss. Pass -Compression CCITTG4, -Compression LZW, or -Compression None only when you actually need to change the encoding.
TIFF Paging X inspects each input file before processing. Single-page TIFFs are skipped, not copied or renamed. This lets you point the splitter at a mixed folder without producing duplicates. The log file records which files were split and which were skipped.
Yes. TIFF Paging X registers as a COM/ActiveX object (TIFFPaging.TIFFPagingX). You can call it from .NET, PHP, Python, VBScript, ASP, Ruby, Perl, and any other COM-compatible environment. The same parameter syntax used on the command line works through the COM Convert method.
Yes. Save the split command in a .bat file and add it to Windows Task Scheduler. The splitter runs unattended at the scheduled time, processes every new multi-page TIFF in the watch folder, and writes a log file for verification. Pair it with a clean-up step that moves processed source files to an archive folder.

 

Start working now!

Download free trial and convert your files in minutes.
No credit card or email required.

⬇ Download Free Trial Windows 7/8/10/11 • 12 MB

Support

Related Topics

Latest News

Newsletter Subscribe

No worries, we don't spam.


© 2026. All rights reserved. CoolUtils File Converters

Cards