Watermark policies and what they cost you
Visible badges, invisible provenance marks and plan-gated removal are three policies with three different bills — in rework, ad rejection and disclosure.
A watermark policy looks like a branding decision and behaves like a production cost. The corner badge doesn't just sit there — it decides whether the clip can be cropped, whether the ad passes review, whether the asset you tested with is the asset you ship, and in a few cases whether your legal team has an opinion about it. Three unrelated policies get filed under the same word, they bill you in three different currencies, and only one of them is something you can switch off.
The three policies
Visible marking. A logo, wordmark or badge composited into the rendered frame. It's part of the pixels once the file exists. Removing it after the fact means cropping, covering or regenerating — there is no undo. Versely's watermark reference makes the general split between visible and invisible marks; this is the visible half, and it's the only half you can see coming.
Invisible provenance marking. A signal embedded in the content itself at generation time, readable by a detector and not by a person. Google's SynthID is the case with the most published detail: DeepMind's own technical page describes it as added at generation and "designed to stand up to modifications like cropping, adding filters, changing frame rates, or lossy compression." It is deliberately not removable by ordinary handling, which is the point of it. It is also a property of the model, not of your account — when Google made the Imagen 4 family generally available in the Gemini API, SynthID marking came with every output. No plan changes that. The longer SynthID breakdown covers what the signal does and doesn't prove.
Plan gating. The policy where the visible mark exists on some tiers and not others. Mechanically this is the same visible mark as the first case; commercially it's a different thing, because it converts an export decision into a billing decision and means the asset you evaluated is not the asset you'd publish.
These three are independent. A file can carry all of them, none of them, or an invisible mark with no visible one — which is the most common state and the one people most often misread as "unwatermarked".
What each one actually bills you
| Visible mark | Invisible provenance mark | Plan-gated removal | |
|---|---|---|---|
| Removable after render | Only by crop, cover or regenerate | No | Only by changing plan and re-rendering |
| Costs you rework | Yes — reframing, masking, re-export | No | Yes — everything tested has to be redone |
| Risks ad rejection | Yes, on paid placements | Not directly | Yes, if a test asset ships by mistake |
| Affects disclosure duties | No | No | No |
| Under your control | Only by choosing a different tool | No — it's the model's | Yes, by paying |
The row that surprises people is the last one. None of the three discharges a disclosure obligation, and none of them creates one either. Synthetic media disclosure is a separate duty that attaches to how you present the content, an AI content label is a platform-side toggle that renders a badge on a post, and an embedded provenance signal is a technical property of the file. Treating any one of them as a compliance checkbox for the others is the most expensive mistake in this whole area, because it's the one you don't discover until someone asks.
What a visible mark costs: rework, then review
The most common plan for a visible badge is "we'll crop it out". That plan has three costs people underestimate.
It changes the frame you composed. A bottom-right badge on a 9:16 vertical cut sits in the same real estate the platform's own UI already occupies — the caption block, the CTA, the profile row. Cropping it out either pushes your subject off-centre or forces a zoom that softens the whole frame. See aspect ratio for why the safe area matters more on vertical than it does on 16:9.
It doesn't survive a resize. Crop to remove a corner and you're no longer at the aspect ratio the placement wants. Re-pad it and the badge area comes back as letterboxing.
Covering it looks like covering it. A blurred patch or a gradient over the corner is legible as a patch to any viewer who's seen one before, especially on paid placements where people are already primed to look for what's being hidden. An upscale pass doesn't help either — upscaling reconstructs detail from what's in the frame, and a burned-in badge is detail.
The honest budget line for a visible mark isn't "one crop". It's: reframe, re-export, re-check against the placement spec, and accept a composition you didn't choose. On a single hero asset that's an afternoon. On a set of 30 variants for a test, it's the reason the test doesn't ship.
Paid review is where the same mark stops being cosmetic. A tool's logo in the corner of your ad is a second brand inside a placement you bought, and reviewers, competitors and the platform's own automated checks all treat that as a signal worth looking at. It also undermines the specific thing most short-form ad creative is trying to do, which is not look like an ad someone assembled in a tool.
Generated creative already carries its own review surface independent of watermarking — what ad review flags on generated creative covers the categories that actually trigger holds, and AI ad disclosure compliance covers the declaration side. A visible tool mark doesn't put you into those categories, but it does volunteer that the asset came from a tool, at exactly the moment you'd rather the conversation were about the product.
The version of this that costs real money is the plan-gated one: you test with marked assets, the test wins, and the winning creative can't be shipped as-is. Either you re-render everything on a tier that removes the mark — which means new files, new IDs, and a fresh review cycle — or you ship the marked version and eat whatever it does to performance. Both are worse than having decided the policy before the test.
Where Versely sits
No watermarks on any plan. Not on the cheapest one, not on images, not on video, not on exports from the editor. There is no tier where a mark appears and no tier where removing it is the upgrade, which means the asset you evaluate is the file you publish — same pixels, same ID, no second review cycle. Plans and credit costs are on pricing, and what changes between them is credit volume and billing cadence, not what comes out of a render.
The part Versely does not control, and won't claim to: provider-embedded provenance signals. Where a model family embeds one at generation time, that happens inside the provider's own pipeline before the file reaches anything Versely does with it. Versely neither adds a marking pass of its own nor strips one out. So the one lever that actually exists is model choice — the model catalog names the provider behind each model it lists, and that's the decision point if an embedded signal on your output matters for a specific project.
Worth stating plainly: Versely does not attach or expose a signed C2PA manifest as a customer-facing feature today. If a client contract requires a checkable, signed edit-history record rather than an anonymous in-content signal, that's a separate requirement to solve, not something a watermark policy answers.
A four-question audit before you standardise on a tool
- Does the export carry a visible mark on the tier I will actually be on? Test on the tier you'll ship from, not the one you evaluated on.
- Does the model embed an invisible signal, and is that a property of the model or of my plan? If it's the model, no amount of paying changes it — only switching models does.
- What does my placement spec do to a corner badge? Run one real asset through the real crop before you commit to a whole campaign.
- What is my disclosure position, independent of both? Decide it once, in writing, and don't let the presence or absence of a mark move it. How labels and detection actually interact is the background reading.
FAQ
If a file has no visible watermark, is it unmarked?
No, and this is the most common misread in the category. A visible badge and an embedded provenance signal are unrelated mechanisms. A file can be visually clean and still carry a detector-readable signal from the model that generated it. The absence of a visible mark tells you about the tool's export policy and nothing about the file's contents.
Does removing a watermark violate anything?
That depends entirely on the terms you agreed to when you generated the file, which is the actual question rather than a technical one. Tools that gate removal behind a tier are gating it because the marked output is licensed differently from the unmarked one. The safe read is that if a tool put a mark there deliberately, removing it is a terms question before it's a Photoshop question.
Can I regenerate a marked asset somewhere else to clean it up?
You can regenerate the concept, not the asset. Feeding a marked frame into an image-to-image or video-to-video pass changes the mark's appearance without reliably eliminating it, and it changes everything else in the frame too. If a marked render is the only version you have, treat it as a reference for a fresh generation rather than a file to repair.
Does a watermark satisfy an AI disclosure requirement?
No. A mark is a property of the file; a disclosure is a statement you make about the content where you publish it. They frequently apply to the same asset at once, and neither substitutes for the other.