Description:
This step removes blank pages from a PDF document.
The Remove Blank Pages workflow step reads an existing PDF document from a specified input file path, analyzes each page, removes pages with no meaningful content, and writes the resulting PDF to a specified output file.
This step provides an efficient way to automate document cleanup before archiving, indexing, OCR processing, document review, printing, or uploading documents into the FlowWright Document Management System.
The step supports:
- Removal of blank pages from PDF documents
- PDF input and output file processing
- Automated document cleanup
- Integration with file system and document workflows
- Preparation of documents for downstream processing
This step can be used for:
- Document preprocessing
- OCR preparation
- Document archival
- Batch document cleanup
- Scanned document processing
- Repository optimization
- Business process automation
Inputs
- inputFilePath – Specify the full path to the PDF document to be processed.
- outputFilePath – Specify the full path where the cleaned PDF document will be saved.
Returns
- True – Blank pages were successfully removed, and the output PDF was created.
- False – The document could not be processed, or the blank pages could not be removed.
Usage:
The Remove Blank Pages step is typically placed before OCR, document upload, indexing, archival, or approval activities within a workflow.
The workflow reads the specified PDF document, removes any blank pages, and writes the cleaned document to the configured output location.
A typical workflow might look like this:

Once the cleaned PDF has been generated, later workflow steps can:
- Upload the document into the DMS
- Perform OCR processing
- Extract document metadata
- Route the document for review
- Archive the document
- Send the document for approval
- Continue document processing workflows
The input PDF file must already exist and be accessible before this step is executed.
Example:
Let’s build and execute the “RemoveBlankPagesDef” example.
- Create a new process definition named “RemoveBlankPagesDef” and open it in Designer mode.
- Drag a “RemoveBlankPage” step to the canvas.
- Connect the dots between the “Start” step and the “RemoveBlankPage” step, as shown above.
- Define a variable or a global to store the result.
- Click the "RemoveBlankPage" step to configure its "Required" properties. Provide a name for the step. Provide the input file path. Provide a variable or global reference to store the output file path and the PDF virtual file path. Click the Save button. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description.

- The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. This is achieved by configuring the step state and percent fields individually, as shown in the images below. Configure the “Logging” using the following properties.

- Save the Process Definition. Create a new Process Instance and execute it. When the workflow reaches the Remove Blank Pages step, FlowWright opens the specified PDF document, analyzes its pages, removes blank pages, and saves the resulting document to the configured output location. If the operation completes successfully, the workflow follows the True return path. If the input file cannot be found, the file is not a valid PDF, the output location is inaccessible, or the document cannot be processed, the workflow follows the False return path. Click the process step to view its properties. The step should successfully generate the cleaned PDF document and return True upon completion. Verify that the output document exists and that blank pages have been removed.

Tips:
- Verify that the input PDF file exists before executing the workflow.
- Store the output PDF in a location accessible to subsequent workflow steps.
- Preserve the original document if it must be retained for auditing or compliance purposes.
- Use workflow variables to dynamically generate input and output file paths.
- Execute this step before OCR or document indexing to improve processing efficiency.
- Use the True and False return paths to implement appropriate success and error handling.
- Combine this step with the Download Document, Create Document, Update Document, Archive Document, or Review Document workflow steps to automate complete document-processing workflows.
Notes:
- The input file must be a valid PDF document.
- The executing process must have permission to read the input file and write the output file.
- The original PDF document is not modified unless the output path is set to overwrite the original file.
- Only blank pages are removed; pages containing text, images, annotations, or other meaningful content are preserved.
- Invalid file paths, inaccessible locations, or corrupt PDF documents may cause the step to return False.
- The workflow should include appropriate error handling for the False return path.
- Removing blank pages before downstream processing can reduce document size and improve OCR, indexing, printing, and storage efficiency.
Definition Sample:
You may download the sample definition(s) from the link provided and later import them (drag-and-drop) into your FlowWright Process Definition (XML file) or Form Definition (HTML file) page.
Note: Verify and complete any missing configuration after importing the sample, including:
- Input file path
- Output file path
- Workflow variable mappings
- File system permissions
- Environment-specific settings
After verifying the configuration, save the Process Definition before execution.