How Watermark Settings Persist Across Every Task and Save

Re-typing the same brand text and dragging the opacity slider to the same spot for every batch is exactly the kind of busywork software should kill. That is the practical value of the way watermark settings persist in Bulk Image Downloader From URL List: the mark you configure once is remembered and reapplied, so a hundred downloads carry the same stamp without you touching the panel again.

What actually gets saved

The watermark you build is stored in the extension’s persistent state (watermarkAppState), and it survives saves. That covers the parts that define how a mark looks:

• Type — a text watermark or an image/logo watermark.
• Size — how large the mark renders relative to each image.
• Opacity — how visible or subtle the stamp sits over the photo.
• Gravity/position — where on the image the mark lands, corner or center.

Because these are remembered, you tune the look once and trust it. Open a new task next week and the same configuration is waiting. You are never reconstructing a watermark from memory or guessing whether you matched last month’s settings.

Why it matters that watermark settings persist

Consistency is the whole reason watermarks exist. A logo that drifts to a different corner, or sits at 40% opacity on one batch and 80% on the next, undercuts the point. Because watermark settings persist, every image processed through the pipeline gets identical treatment. That is what makes a set of downloads look like it came from one source rather than a dozen ad-hoc sessions.

It also reduces mistakes. You are not re-entering a hex value or re-uploading a logo each time, so there is no chance of grabbing last month’s wrong file or fat-fingering the brand text. The settings you trust today are the settings that run tomorrow.

The validation guardrail

There is one sensible check worth knowing about. If you enable an image watermark, the extension blocks you from turning it on without actually selecting an image. That validation stops a common failure: thinking your logo is stamping every download when no file was ever attached, then discovering a thousand bare images later. The guard fails loud and early instead of silently doing nothing, which is precisely what you want from a setting meant to run unattended.

How it fits the download pipeline

The watermark is applied on download by a background Web Worker, alongside any resize, format conversion, or EXIF stripping you have set. Everything runs client-side in your browser using Canvas — nothing is uploaded to a server for stamping. So the persistence is not just a UI convenience; the saved configuration is what the worker reads when it processes each file. The fact that watermark settings persist means the recipe rides along with every batch until you deliberately change it. It even travels through CSV export and import, where a watermark-enabled flag records which tasks carry a mark.

If you watermark for a living, or even just to protect a portfolio, the payoff is simple: configure the mark once, then stop thinking about it. You can grab the extension on the Chrome Web Store and build a watermark whose settings persist across every task and save you make.