Image Watermarking

Stamp a logo or text mark onto images before they leave the app.

moderate Media & Video

What it adds

An automatic overlay of a logo or text mark applied to images at the point they are served, downloaded, or shared.

What your agent is told to do

1
Apply the mark when the image is delivered, not when it is uploaded, and cache the marked variant. Burning the mark into the stored file at upload means changing the logo requires reprocessing every asset ever uploaded.
2
Always keep the unmarked original, and serve it to the owner and to anyone with an explicit right to the clean file. Reuse the app's existing secure download path to decide who that is.
3
Size and position the mark as a proportion of the image rather than in fixed pixels, so it reads the same on a small thumbnail and on a large photograph.
4
Decide explicitly what happens to the original metadata: strip location and camera data on public delivery, or preserve it, but make it a stated choice rather than whatever the encoder happens to do.
5
Do not treat this as copy protection. A watermark deters casual reuse and nothing more, so do not build access rules that assume the marked image cannot be cropped or edited.

Edge cases it handles

A mark sized in fixed pixels dominates a thumbnail and disappears on a large photo. Scale it as a percentage of the shorter edge and set a floor so it stays legible.
The owner must always be able to retrieve the clean file. Store the original untouched and gate access to it through the app's existing per-file permission checks.
A dark mark vanishes on a dark photo and a light one vanishes on a bright sky. Sample the region under the mark and choose a treatment, or add a subtle shadow or outline so it survives both.
Applying the mark on upload freezes it forever. Generate marked variants on delivery and cache them, and invalidate that cache whenever the mark, its position, or its opacity changes.
Uploaded photos carry location, device, and timestamp metadata that should usually not be published. Decide deliberately whether the delivered variant strips or preserves it, and apply the same rule everywhere.
Generating a marked variant on the first request adds latency to that request. Serve a placeholder or the pending state rather than a broken image, and warm the common sizes.
The mark must not obscure the subject of every image by default. Offer a position choice and a default that sits in a corner with a margin.
Marked variants must respect the same access rules as the original. A public marked URL must not become a way to enumerate private assets.

Definition of done

Marks are applied on delivery and cached, not burned into the stored original.
Changing the mark or its settings invalidates cached variants without reprocessing originals.
The unmarked original is retained and reachable only by permitted users.
The mark scales proportionally and stays legible across image sizes and brightness.
Metadata handling on delivered variants is an explicit, consistent decision.
Marked variants enforce the same access rules as the source file.
The feature matches the existing design system.
No existing functionality is broken.

Related features

Picture-in-Picture Mode

Audio Waveform Scrubber

Hover Video Preview

How it works

1

Copy the link

Grab the Markdown instruction URL for this feature.
2

Give it to your AI

Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
3

It inspects, then implements

Your agent reads your existing app first, then adds the feature to fit it.

Works with your stack

These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.

Need it tighter than that? Customize the feature and tell it exactly what you're running.