Watermark Image API

Pricing

Rating

Developer

Actor stats

Categories

Share

🖼️ Watermark image API for text and logo overlays

Watermark Image API adds text, logo, or tiled watermarks to images from URLs, uploads, Apify key-value-store files, or base64 data URLs. Use it when you need repeatable image watermarking for product photos, brand assets, proof previews, campaign images, content operations, or an API workflow that has to process many images the same way.

For a quick first run, keep the prefilled sample images, leave Watermark text as Demo, and start the Actor. The Actor saves each successful watermarked image as a file in Apify key-value storage and returns a clean dataset row with the source image, output URL, output format, and applied watermark settings.

You can run this image watermark API from Apify Console, call it through the Apify API, schedule runs, connect webhooks, or export the dataset as JSON, CSV, Excel, XML, RSS, or HTML. You do not need a third-party image-processing account, source website login, cookies, or an external API key.

✅ What this Actor does

• Adds a text watermark, logo watermark, or both to each image.
• Accepts direct image URLs, uploaded files, key-value-store keys, and base64 data URLs.
• Saves one dataset row per successfully watermarked image.
• Saves each generated image file to Apify key-value storage and returns a direct outputUrl.
• Supports PNG, JPEG, and WebP output.
• Supports 9 placement positions, opacity, rotation, padding, custom offsets, and repeated tiled watermarks.
• Supports font family, optional custom font URL, text color, bold text, outline width, and text background opacity.
• Supports logo scale plus shared placement, opacity, rotation, and tiled settings.
• Can resize large output images by maximum width or height while keeping aspect ratio.
• Can include a small base64 data URL in the dataset when explicitly requested.
• Skips failed image attempts from the dataset and keeps processing the rest of the batch when possible.

The dataset contains successful watermarked-image rows only. Failed source downloads, missing KV files, invalid image bytes, and other handled per-image issues are reported in logs and in the run summary stored under OUTPUT.

📦 Data you can export

Each output row represents one successfully watermarked image. Fields include:

• sourceImage - the submitted image URL, uploaded-file reference, KV Store key, or safe base64 label.
• outputUrl - the generated image file saved in Apify key-value storage.
• outputFormat - png, jpeg, or webp.
• watermarkText - the text that was applied, or null for logo-only outputs.
• logoApplied - whether a logo or image watermark was applied.
• position - the applied watermark position.
• opacity - the applied opacity from 1 to 100.
• rotation - the applied rotation in degrees.
• tiled - whether the watermark was repeated across the image.
• base64Output - an optional data URL when requested and small enough; otherwise null.

Use outputUrl for normal downstream workflows. Use base64Output only when your integration needs image bytes inside the dataset row and the generated file is small enough for that output mode.

🚀 How to run

1. Add one or more images in Images. You can upload files or paste direct image URLs.
2. Add Watermark text, Logo image, or both.
3. Keep Position, Opacity, and Output format at the defaults for a simple first run.
4. Start the Actor.
5. Open the dataset for output rows, or open the key-value store to browse generated image files.

For API workflows that already hold image bytes, pass base64 image data as data URLs in Base64 images. For storage workflows, pass existing Apify key-value-store keys in Images or Logo image.

⚙️ Input

{
"imageFiles":[
"https://raw.githubusercontent.com/ParseForge/apify-assets/65f2790e17ebc08b3c4ae5ca92cbb43a444c2ab1/watermark-image-api/original.avif"
],
"watermarkText":"Demo",
"position":"bottom-right",
"opacity":50,
"outputFormat":"png"
}

🖼️ Source images

Use Images for direct image URLs, uploaded files, or Apify key-value-store keys. Each item becomes one attempted watermarked image. Use Base64 images only for data URLs such as data:image/png;base64,....

✍️ Text and logo

Use Watermark text for text overlays. Use Logo image for a logo or image overlay from an upload, URL, KV key, or data URL. When both are provided, the Actor applies both.

Text controls include font family, custom font URL, text color, font weight, text size, outline width, and optional background opacity. Logo controls include logo size. Both text and logo watermarks share placement, opacity, rotation, padding, offsets, and tiled mode.

📦 Output settings

Choose PNG, JPEG, or WebP. Use JPEG/WebP quality for lossy formats. Use Maximum output width or Maximum output height when you want the generated image to fit inside a size cap while preserving aspect ratio.

📄 Output example

{
"sourceImage":"https://raw.githubusercontent.com/ParseForge/apify-assets/65f2790e17ebc08b3c4ae5ca92cbb43a444c2ab1/watermark-image-api/original.avif",
"outputUrl":"https://api.apify.com/v2/key-value-stores/abc123/records/watermarked_1.png",
"outputFormat":"png",
"watermarkText":"Demo",
"logoApplied":false,
"position":"bottom-right",
"opacity":50,
"rotation":0,
"tiled":false,
"base64Output":null
}

💳 Pricing

This Actor uses pay-per-event pricing. You are charged for each image that is successfully watermarked and saved. Failed image attempts, invalid inputs, and runs that do not save watermarked images do not create watermarked-image events.

There is no separate Actor-start charge in this pricing setup. The per-image price starts at $2.25 per 1,000 successful images on the FREE usage tier, with lower prices on higher Apify tiers.

⚠️ Limits and caveats

• Source image URLs must be reachable during the run.
• Uploaded files and KV keys must point to image bytes the Actor can decode.
• Base64 image input must be supplied as a data URL.
• Animated images are processed as static images.
• The dataset contains only successful output rows. Check logs and the OUTPUT key-value-store summary for skipped images.
• Base64 output is optional and bounded to avoid oversized dataset rows.
• The Actor adds visible watermarks. It does not provide DRM, legal advice, invisible watermarking, or assured removal resistance.

❓ FAQ

🔐 Do I need an image API key?

No. The Actor processes images inside the Apify run and does not ask for a third-party image-processing API key, source account, cookies, or login.

🔁 Can I add the same watermark to many images?

Yes. Add multiple image URLs, uploads, KV keys, or data URLs. Each successful image creates one output file and one dataset row.

🏷️ Can I use text and a logo together?

Yes. Fill Watermark text and Logo image in the same run to apply both overlays.

🧱 Can I create a tiled stock-photo preview watermark?

Yes. Enable Repeat across image and set Repeat spacing. The same tiled setting applies to text and logo watermarks.

🔌 Can I use this through the Apify API?

Yes. Run the Actor through the Apify API, pass the same input fields, then read the dataset rows and generated files from the run storage.

📝 Changelog

• 0.0: Initial release.

🆘 Support

For issues, questions, or feature requests, file a ticket and I'll fix or implement it in less than 24h 🫡

🔗 Other actors

• Web Images Scraper ↗ - Extract image URLs and optional saved files from public webpages.
• Unsplash Image Scraper ↗ - Collect Unsplash image search results for design and content research.
• Twitter Screenshot Generator ↗ - Capture clean images of public X posts.
• Craiyon AI Image Creator ↗ - Generate prompt-based images and save Apify download links.
• Font Detector ↗ - Detect fonts and font files from public web pages.

Made with ❤️ by Maxime Dupré