Actions80
- Add Attachment To PDF
- Add Barcode To PDF
- Add Form Fields To PDF
- Add HTML Header Footer
- Add Image Stamp To PDF
- Add Image Watermark To Image
- Add Margin To PDF
- Add Page Number To PDF
- Add Text Stamp To PDF
- Add Text Watermark To Image
- AI-Invoice Parser
- AI-Process Contract
- AI-Process HealthCard
- Classify Document
- Compress Image
- Compress PDF
- Convert HTML To PDF
- Convert Image Format
- Convert JSON To Excel
- Convert Markdown To PDF
- Convert PDF To Editable PDF Using OCR
- Convert PDF To Excel
- Convert PDF To PowerPoint
- Convert PDF To Word
- Convert To PDF
- Convert URL to PDF
- Convert VISIO
- Convert Word to PDF Form
- Create Images From PDF
- Create PDF/A
- Create Swiss QR Bill
- Crop Image
- Delete Blank Pages From PDF
- Delete Unwanted Pages From PDF
- Split PDF By Barcode
- Disable Tracking Changes In Word
- Enable Tracking Changes In Word
- Extract Attachment From PDF
- Extract Form Data From PDF
- Extract Pages From PDF
- Extract Resources
- Extract Table From PDF
- Extract Text By Expression
- Extract Text From Word
- Fill PDF Form
- Find And Replace Text
- Flip Image
- Flatten PDF
- Generate Barcode
- Generate Document Single
- Generate Documents Multiple
- Get Document From Pdf4me
- Get Image Metadata
- Get PDF Metadata
- Split PDF By Swiss QR
- Get Tracking Changes In Word
- Image Extract Text
- Linearize PDF
- Merge Multiple PDFs
- Overlay PDFs
- Parse Document
- Protect PDF
- Read Barcode From Image
- Read Barcode From PDF
- Read SwissQR Code
- Remove EXIF Tags From Image
- Repair PDF Document
- Replace Text With Image
- Replace Text With Image In Word
- Resize Image
- Rotate Document
- Rotate Image
- Rotate Image By EXIF Data
- Rotate PDF Page
- Sign PDF
- Split PDF By Text
- Split PDF Regular
- Unlock PDF
- Update Hyperlinks Annotation
- Upload File To PDF4me
Overview
The node provides a "Linearize PDF" operation that optimizes PDF files for faster and more efficient web viewing or printing. Linearization rearranges the internal structure of a PDF to enable progressive loading, meaning users can start viewing the first pages before the entire file is downloaded. This is especially useful for large PDFs accessed over the internet.
Common scenarios include:
- Preparing PDFs for online distribution where quick preview and access are important.
- Optimizing PDFs for printing with specific quality or compression profiles.
- Reducing file size while maintaining usability for web or print.
Practical example: A user uploads a scanned PDF document and wants to linearize it for embedding in a website so visitors can quickly view the content without waiting for full download.
Properties
| Name | Meaning |
|---|---|
| Input Data Type | Choose how to provide the PDF file to linearize. Options: Binary Data (from previous node), Base64 String (direct base64 encoded content), URL (link to PDF file). |
| Input Binary Field | Name of the binary property containing the PDF file when using Binary Data input type. Default is "data". |
| Base64 PDF Content | Base64 encoded string of the PDF document content, used if Input Data Type is Base64 String. |
| PDF URL | URL to the PDF file to linearize, used if Input Data Type is URL. |
| Output File Name | Desired name for the output linearized PDF file. Default is "linearized_document.pdf". |
| Document Name | Name of the source PDF file for reference purposes. Default is "document.pdf". |
| Optimization Profile | Selects the optimization profile for linearization. Options include: Web (fast loading, progressive display), Max (maximum compression), Print (optimized for printing), Default (balanced), WebMax, PrintMax, PrintGray, Compress, CompressMax. |
| Advanced Options | Collection for additional custom options via JSON profiles to fine-tune the linearization process. Users can specify custom API call properties here. |
| Binary Data Output Name | Custom name for the binary data field in the node's output. Default is "data". |
Output
The node outputs the linearized PDF as binary data under the specified binary data output name (default "data"). The output includes:
json: Metadata about the processed file, typically including the output file name.binary: The actual linearized PDF file content, ready for further use or saving.
This allows subsequent nodes to easily consume the optimized PDF either by referencing the binary data or exporting it.
Dependencies
- Requires an external PDF processing service accessible via API to perform the linearization.
- Needs proper API authentication configured in n8n credentials (an API key or token).
- Network access to fetch PDF from URL if URL input type is selected.
Troubleshooting
Common issues:
- Invalid or inaccessible PDF URL leading to fetch errors.
- Incorrect base64 content format causing decoding failures.
- Missing binary data in the specified input field.
- API authentication errors due to invalid or missing credentials.
- Unsupported PDF formats or corrupted files causing processing failures.
Error messages and resolutions:
- "Failed to fetch PDF from URL": Check URL correctness and network accessibility.
- "Invalid base64 content": Verify the base64 string is properly encoded.
- "Binary data not found": Ensure the binary property name matches the input data.
- "Authentication failed": Confirm API credentials are correctly set up in n8n.
- "PDF processing error": Validate the PDF file integrity and supported format.
Links and References
- PDF Linearization Concept
- PDF Optimization Profiles Documentation (for advanced custom profiles)
- Base64 Encoding Reference
This summary is based on static analysis of the node's execute method and provided property definitions.