- What's Hidden? Scan
- Quick Tamper Check
- Deep Forensic Scan
- AI-Generated Detection
- Manipulation & Clone Scan
- Watermark Detection Scan
- Geo-Tag Presence Audit
- AI Pixel-Forensics
- Forensics PDF Report
- Home
- Workflows
Batch automation
Build a pipeline once. Run it forever.
StegoPixel's workflow builder turns repetitive image work into a repeatable, auditable run. Chain 45 node types into a linear pipeline, or start from one of 54 built-in presets covering privacy, forensics, metadata, steganography, authentication and image processing — all executing locally.
How a workflow runs
Nodes execute in the order you place them and hand their results to the next step. There is no hidden graph state to reason about — what you see in the list is what runs.
-
Collect the input
Start from a folder, optionally including subfolders. The node produces the working file list that every later step sees. Two further input nodes read from saved collections or stored search results, so a pipeline can be re-run over a set you defined earlier rather than a folder path.
-
Transform, clean or inspect
Add metadata, privacy, file, image, steganography or analysis nodes. Each one operates on the current file list and can replace it with its own output.
-
Run it
Watch per-node and per-file progress, with pause, resume and cancel available at any point. Long batches stay interruptible.
-
Collect the evidence
Finish with a report, an export, an archive or a hash manifest. Every run is recorded in execution history so you can see exactly what happened.
The node editor is a searchable list you can reorder by dragging. If you would rather answer questions than wire nodes, the guided wizard walks you through the same pipeline one decision at a time.
The 45 node types
Grouped by what they do. Names are shown as they appear in the app's node type registry.
| Node | What it does |
|---|---|
Input_Folder | Collects image files from a folder, with an option to include subfolders. |
Input_Collection | Starts from a saved collection rather than a folder path, so the same set can be re-run later. |
Input_SearchResult | Starts from a stored search result set. |
| Node | What it does |
|---|---|
Metadata_Read | Reads EXIF, XMP and IPTC tags and makes them available to later nodes and reports. |
Metadata_Write | Writes standard EXIF string tags or custom key/value pairs as XMP. |
Metadata_Remove | Strips metadata, either wholesale or by selected tag group. |
Metadata_Validate | Checks tag values for inconsistencies and reports what it found. |
| Node | What it does |
|---|---|
File_Rename | Renames with a pattern supporting {n}, {n:000}, {ext} and {name}. |
File_Move | Moves files to a destination, optionally organised into subfolders. |
File_Copy | Copies without touching the originals — useful as a safe first step. |
File_Delete | Deletes files. Defaults to the Recycle Bin; permanent deletion must be requested explicitly. |
File_Sort | Reorders the working file list by capture date, name, size and other criteria. |
| Node | What it does |
|---|---|
Image_Resize | Resizes to target dimensions or by percentage. |
Image_Convert | Converts between the supported image formats. |
Image_Watermark | Applies a visible watermark overlay. |
Image_Enhance | Runs enhancement filters such as contrast, sharpening and level correction. |
| Node | What it does |
|---|---|
Privacy_RemoveGps | Removes GPS location data from the file. |
Privacy_RemovePersonal | Removes personal and identifying fields such as camera serials and author details. |
| Node | What it does |
|---|---|
Stego_Encode | Hides a payload in image pixels via LSB embedding, optionally encrypted. |
Stego_Decode | Extracts a pixel-embedded payload, decrypting it when a passphrase is supplied. |
Stego_MetadataEncode | Hides a payload in a metadata channel instead of the pixels. |
Stego_MetadataDecode | Extracts a payload hidden in a metadata channel. |
Stego_MetadataDetect | Reports whether a metadata channel carries a payload, without extracting it. |
Stego_Analyze | Analyses a carrier for signs of hidden data across pixels and metadata. |
| Node | What it does |
|---|---|
Analysis_Forensics | Runs the combined forensic scan and stores its findings for reporting. |
Analysis_ELA | Error Level Analysis — surfaces regions recompressed at a different quality level. |
Analysis_Noise | Noise analysis for inconsistencies across the image. |
Analysis_NoiseConsistency | Maps how uniform the noise floor is, which tends to break where content was inserted. |
Analysis_NoiseResidual | Isolates the residual signal left after denoising. |
Analysis_SnrMap | Builds a per-region signal-to-noise map. |
Analysis_NoiseRainbow | Renders noise as a false-colour rainbow for visual inspection. |
Analysis_LevelSweep | Sweeps tonal levels to expose faint structure and edge artefacts. |
Analysis_Gradient | Luminance-gradient analysis with selectable operators and modes. |
Analysis_Pca | Principal component analysis over colour channels, in several modes. |
Analysis_Watermark | Looks for embedded watermark carriers. |
Analysis_BlockSimilarity | Block-level similarity search for duplicates and copy-move manipulation. |
Analysis_GeoTag | Audits location tags and records map references in the report. |
| Node | What it does |
|---|---|
AI_Detect | Heuristic synthetic-origin detection in four modes: metadata generator signatures, pixel statistics (DCT / noise / CFA), a frequency-domain watermark carrier scan, or a unified pass that combines every available family — metadata signatures, metadata plausibility, stripped metadata, pixel statistics, carrier scan, Stable Diffusion watermark decode and C2PA. Hand-written statistics, not a trained model. |
C2PA_Check | Parses C2PA Content Credentials embedded in the file and reports the provenance claim they contain — creator, tooling and manifest contents. It surfaces the claim; it does not validate a cryptographic chain of trust. |
| Node | What it does |
|---|---|
Sign_Image | Signs an image using an RSA (2048/4096) or ECDSA (P-256/384/521) key, storing the signature in the file's metadata. Keys are held in a local key store as PKCS#8 or PEM. |
Verify_Signature | Checks a stored signature and records the result for the report. |
| Node | What it does |
|---|---|
Output_Export | Exports accumulated analysis results, including hash manifests and metadata tables. |
Output_Report | Renders a report of the run — HTML or PDF — from everything captured upstream. |
Output_SaveImage | Writes the processed image to a destination folder. |
Output_Archive | Packages the results into a ZIP archive. |
Preset library
54 ready-made pipelines across 8 categories. Start from a preset and adjust the parameters, or use it as a worked example of how the nodes fit together.
- Hide Text Message
- Hide Image in Image
- Hidden Metadata Channel
- Extract Hidden Data
- Steganography Scan
- Encrypted Secret Channel
- Encrypted Metadata Channel
- Archive Hidden in Image
- Strip GPS Location
- Full Anonymization
- Prepare for Web Sharing
- Strip All Metadata
- Minimal Cleanup (Keep GPS)
- GPS-Free Web Gallery
- Sign Images
- Verify Signatures
- C2PA Provenance Check
- Full Authenticity Report
- Sign Copies
- Provenance & AI Audit
- Resize for Web
- Convert Image Format
- Convert to WebP
- Batch Watermark
- Batch Enhance
- Batch Sharpen
- Fix Exposure (Levels)
- Photo Archive Pipeline
- Read & Export Metadata
- Clean Metadata & Report
- Apply Copyright & Author
- Validate Metadata
- Add Custom Project Tags
- Apply Saved Template
- Export Metadata to PDF
- Order by Capture Date
- Order Newest First
- Batch Rename Sequence
- Sort & Rename In Place
- Find Near-Duplicate Images
- Search & Copy Matches
- Collect & Move to One Folder
- Archive to ZIP
- Collect & Copy to One Folder
- Backup & Hash Manifest
Reports & outputs
A pipeline is only useful if it leaves you something you can hand to somebody else. StegoPixel writes reports that stand on their own.
| Output | Format | Typical use |
|---|---|---|
| Forensic report | HTML · PDF | A readable findings document with embedded result imagery and verdicts. |
| Metadata export | JSON · CSV · HTML | Flat tag tables including raw hex values, for spreadsheets or further processing. |
| Hash manifest | JSON | SHA-256 and SHA-512 digests per file, for integrity and transfer verification. |
| Processed images | Same as source, or converted | Resized, converted, watermarked or enhanced output written to a folder you choose. |
| Archive | ZIP | Results packaged into a single deliverable. |
Safety & control
Batch operations touch a lot of files at once, so the defaults lean towards undo.
- Backups before destructive steps — configurable, and on by default.
- Recycle Bin by default — permanent deletion is a separate, explicit choice.
- Save-a-copy default — cleaning an image writes a new file rather than overwriting the original.
- Validation before the run — the builder checks the pipeline for missing inputs and impossible steps first.
- Pause, resume, cancel — available while a batch is running.
- Execution history — per-run logs retained for a configurable window, then pruned automatically.
Nothing is simulated or sandboxed — a pipeline does exactly what you configured to the files you selected. That is why backups are on by default and why deletion prefers the Recycle Bin. Dry-run a pipeline on a copy folder first if it is new to you.