When product photos, portfolio images, or review previews all need the same label such as © Example, SAMPLE, or DRAFT, editing each file manually becomes repetitive very quickly. A better fit for repeated work is to define the processing steps once and apply them across the whole batch.
Browser Kitty Image Pipeline Builder lets you add multiple JPEG, PNG, and WebP images, connect a flow such as Resize → Text Watermark → Output, preview intermediate results on a representative image, save outputs individually or as ZIP, and store the workflow as a reusable Recipe.
Know what the Text Watermark node can control
In Image Pipeline Builder v1.0.0, Text Watermark controls the text, font family, font size, color, opacity, position, margin, and rotation. Position can be chosen from nine anchors: top-left, top, top-right, left, center, right, bottom-left, bottom, or bottom-right.
v1.0.0 is specifically a text-watermark workflow. It does not include a dedicated Image Watermark node for overlaying a PNG logo or another image.
| Setting | Purpose |
|---|---|
| Text | Watermark text such as ©, SAMPLE, or DRAFT |
| Font / Size / Color | Control the appearance and scale of the text |
| Opacity | Balance visibility against covering too much of the image |
| Position / Margin | Choose one of nine anchors and control edge spacing |
| Rotation | Rotate the watermark text when needed |
Resize first when you want watermark sizing to match the final output
When source images have very different dimensions, the same font size can look proportionally different. If you already know the final web or delivery size, using Resize → Text Watermark makes it easier to tune the watermark against the final pixel dimensions.
Text Watermark → Resize is also valid, but then the watermark is drawn on the source-sized image and scaled down with everything else. Pipeline order is execution order, so changing node order can change the visual result.
Preview Before / After on a representative image before Batch processing
Adding a batch does not mean you need to process every image immediately. Select the node and switch between Before and After on a representative image to check whether the text is too large, blends into the background, or covers an important subject.
The same color and opacity can behave very differently on bright and dark photos. When possible, preview more than one representative background before the full Batch run.
Choose JPEG, PNG, or WebP in the same watermark workflow
Output nodes can encode JPEG, PNG, or WebP. JPEG and WebP also expose quality settings, so a single Pipeline can handle Resize → Text Watermark → WebP instead of requiring separate tools for each stage.
JPEG cannot preserve transparency, so transparent PNG or WebP input is flattened against the configured background color when exported as JPEG. PNG remains an option when transparency needs to survive.
Keep batch output organized with filename templates and multiple Outputs
Output filenames can use {name}, {index}, {index:N}, {width}, and {height}. A template such as {name}-watermarked makes processed files easy to distinguish, and duplicate paths are automatically disambiguated with suffixes such as -2 or -3.
One output port can connect directly to multiple downstream branches, so the same watermark stage can feed both a 1600 px web image and a 400 px thumbnail. Separate ZIP folders per Output can keep those deliverables organized.
Batch execution processes images sequentially and separates failures
Run the Pipeline to apply it across all added images. Batch execution is intentionally sequential—one image at a time—to reduce peak memory usage. If one image fails, the remaining files continue, and failed results are shown separately from successful output.
Very large images, large batches, many branches, and high-resolution previews or outputs can still consume substantial device memory. Browser and device limits vary, so there is no fixed image-count guarantee for every environment.
Save repeated watermark workflows as Recipes
If you regularly run the same sequence—such as resize to 1600 px, add © Example at bottom-right, export WebP at quality 82, and append -watermarked—register the current Pipeline as a Recipe. Next time, select new images from the Recipe card and run the same settings directly.
Recipes store the graph and settings, not the source images or generated files. Apply a Recipe to the Canvas when you want to edit the saved graph before running it again.
Re-encoding changes how EXIF, GPS, and ICC profiles are handled
Image Pipeline Builder creates newly encoded output files in the browser and does not intentionally copy the source EXIF or GPS metadata. That can be useful for web derivatives where location metadata should not carry forward, but keep the original separately when capture time or camera metadata matters.
Embedded ICC profile preservation is also not guaranteed, so the workflow is not intended for strict color-managed print production. Keep original files untouched and treat the batch output as derived assets for web, review, or general-purpose image processing.
Step by step
- Open Image Pipeline Builder and add multiple JPEG, PNG, or WebP files from the Images node or Images screen.
- Add a Text Watermark node and connect a flow such as Images → Text Watermark → Output. Put Resize before Text Watermark when you want watermark sizing to match a standardized final output size.
- Set the watermark text, font, font size, color, opacity, one of the nine positions, margin, and rotation.
- Switch between Before and After on a representative image and check that the watermark is readable without covering important content.
- In Output, choose JPEG / PNG / WebP, quality, filename template, and an optional ZIP folder.
- Run the Pipeline across the full batch and review successful and failed results separately.
- Save outputs individually or download the batch as a ZIP.
- Register the workflow as a Recipe for repeated use, and save Pipeline JSON as a portable backup when needed.
Image Pipeline Builder
Build reusable image-processing flows with nodes and apply the same steps across multiple JPEG, PNG, and WebP images.
Tips and limitations
- When source dimensions vary widely, resize before watermarking so font size can be tuned against the final output dimensions.
- Preview both bright and dark images to make sure the selected color and opacity remain readable across the batch.
- Keep the original files separately. Output is newly encoded, so EXIF / GPS and ICC profile behavior differs from the source.
- Labels such as SAMPLE or DRAFT can communicate usage status, but a watermark is not a technical mechanism that prevents copying.
Frequently asked questions
Can I add the same watermark to multiple images at once?
Yes. Build a Pipeline containing Text Watermark and run it across the added JPEG, PNG, and WebP files. Batch execution processes the images sequentially.
Can I use a logo image as the watermark?
Not with the dedicated watermark feature in v1.0.0. Text Watermark handles text; there is no dedicated Image Watermark node for PNG logos.
Can I resize and watermark in the same batch?
Yes. Connect Resize → Text Watermark → Output to perform resizing, watermarking, and export as one reusable workflow.
Can I add the watermark while converting to WebP?
Yes. Choose WebP in Output. JPEG and PNG are also supported, and JPEG/WebP expose quality settings.
Can I change watermark opacity and position?
Yes. You can configure the text, font, size, color, opacity, one of nine positions, margin, and rotation.
Are EXIF and GPS metadata preserved?
The app does not intentionally copy source EXIF or GPS metadata into newly encoded output. Keep the original if that metadata must be retained.
Can I reuse the same watermark settings later?
Yes. Save the Pipeline as a browser-local Recipe for quick reuse, or save Pipeline JSON when you need a portable backup.
Are the images uploaded to a server?
Image decoding, processing, preview, encoding, and ZIP generation run in the browser. The standalone build uses connect-src 'none' and does not use a cloud image-processing API.