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
This node operation removes EXIF metadata tags from image files. EXIF tags often contain information such as camera settings, location data, and timestamps embedded in images. Removing these tags is useful for privacy reasons, reducing file size slightly, or preparing images for environments where metadata should be stripped.
Common scenarios include:
- Preparing images for public sharing without revealing location or device details.
- Cleaning images before archival or compliance with privacy regulations.
- Reducing metadata clutter in image processing workflows.
Practical example: You receive user-uploaded photos containing sensitive location data. Using this node, you can strip all EXIF tags before storing or further processing the images.
Properties
| Name | Meaning |
|---|---|
| Input Data Type | How the image file is provided: - Binary Data (from previous node) - Base64 String - URL to image file |
| Input Binary Field | Name of the binary property containing the image file (used if Input Data Type is Binary Data) |
| Base64 Image Content | Base64 encoded string of the image content (used if Input Data Type is Base64 String) |
| Image URL | URL pointing to the image file (used if Input Data Type is URL) |
| Output File Name | Desired filename for the output image after EXIF tags are removed |
| Image Type | Type/format of the image: JPG or PNG |
| Async | Whether to process the image asynchronously (true/false) |
| Binary Data Output Name | Custom name for the binary data field in the node's output |
Output
The node outputs the cleaned image file with all EXIF tags removed. The output includes:
- A JSON object representing the processed item.
- A binary data field containing the cleaned image file, named according to the "Binary Data Output Name" property (default is "data").
- The binary data contains the image content without any EXIF metadata.
No additional metadata or textual output is provided beyond the cleaned image binary.
Dependencies
- Requires access to the image file either via binary input, base64 string, or a reachable URL.
- No explicit external API keys or services are indicated by the code; processing appears to be handled internally or via bundled dependencies.
- The node supports asynchronous processing, which may require appropriate n8n workflow configuration.
Troubleshooting
- Invalid Input Data: If the input image data is malformed or the URL is unreachable, the node will likely throw an error. Ensure the input data matches the selected input type.
- Unsupported Image Types: Only JPG and PNG formats are supported. Providing other formats may cause errors.
- Async Processing Issues: If asynchronous processing is enabled but the environment does not support it properly, unexpected behavior might occur. Try disabling async mode if issues arise.
- Output Binary Naming Conflicts: If multiple nodes output binary data with the same name, consider customizing the "Binary Data Output Name" to avoid conflicts.