Clipchamp does not add a watermark. That is Microsoft's own wording, on its own support page, about its own product: "Good news, the Clipchamp video editor does not add a visual, audio, or any other kind of watermark to your video editing projects or exported videos." Microsoft's plans page repeats it from the other direction — the free plan "Includes core editing tools, free stock media, and watermark-free video exports up to 1080p (full HD)."
If your project uses a premium asset, the official answer is not "you get a watermark" but "no watermark gets added but you will not be able to export and save your video until you upgrade." The block is on the export button, not on the picture.
So a mark that reached a file you actually have came from one of four places, and none of them is the renderer:
1. An asset you imported that already carried a mark.
2. A text, sticker or logo layer you placed on the timeline yourself.
3. A premium asset's hint in the preview — a user-interface overlay, never written into the file.
4. The container's metadata tags — not a visible mark at all.
Rows one and two are pixels and are cleared by deleting the layer and exporting again. Row four is the only one a file tool can touch. And the idea that re-exporting removes a mark is testable, so we tested it: the same mark measured 26.49 dB against a clean render before re-exporting and 26.48 dB after. Exporting again changed nothing that matters.
The official position is unusually clear, so it is worth quoting rather than paraphrasing. From Microsoft's support page titled Does Clipchamp add a watermark to videos?:
"Good news, the Clipchamp video editor does not add a visual, audio, or any other kind of watermark to your video editing projects or exported videos."
And on the same page, for personal accounts that use a premium asset:
"if you add premium stock media files to your project or use a feature that is not included in the plan that your Clipchamp account is on, no watermark gets added but you will not be able to export and save your video until you upgrade to the plan that includes the premium option. In such a case, Clipchamp will show small visual hints in the user interface to highlight the paid features that aren't included in your plan."
Two things follow. The mark you may have seen over a premium clip is interface, drawn by the editor over its own preview to tell you the clip is not licensed to you. It is not a stamp on your media, and the official remedy is not a remover — it is either swapping the asset or upgrading. The second thing is that the same page has a section headed "Add your own watermark", which is the only route by which a Clipchamp mark reaches a Clipchamp export: you put it there.
Where the sources disagree, honestly. A Microsoft Q&A thread dated 11 July 2023 — answered by a community volunteer, not by Microsoft staff — says the opposite: "There will be a watermark on your saved video if you add premium stock or a feature that is not included in the free plan such as brand kit," and "You will be presented with options of how to export with or without a watermark in such a case." Several third-party pages still repeat that older answer as current fact. We cannot settle it for your account: Clipchamp needs a sign-in, this machine has none, and we did not test a premium export. What we can say is that both accounts describe the mark as tied to premium assets, and neither one describes Clipchamp stamping a watermark onto your own footage.
The most common piece of advice in this niche is that putting a marked file back through an editor and exporting again will shake the watermark loose. That is a measurable claim, so the fixture below measures it. One 1920x1080 timeline at 30 fps, four seconds, H.264 CRF 20, with the mark modelled as a 320x90 corner block at (1560, 960) and ordinary container tags written at the same time.
| File | What it is | PSNR against a clean export |
|---|---|---|
clean.mp4 | Generation 1, nothing over the picture | — (it is the reference) |
marked.mp4 | Generation 1, mark composited in | 26.49 dB |
reenc.mp4 | Generation 2 — marked.mp4 encoded again, nothing repaired | 26.48 dB |
| - inside the mark's box, before | The marked rectangle | 7.9658 dB |
| - inside the mark's box, after | The same rectangle, one generation later | 7.9656 dB |
Read the second and third rows together. Re-exporting moved the mark's footprint from 26.49 dB to 26.48 dB, and inside the rectangle from 7.9658 dB to 7.9656 dB. The advice does not survive contact with a measurement: a burned-in mark is part of the picture, and encoding the picture again encodes the mark again. A second generation is not free, either — it costs a little quality everywhere. What it does not do is subtract anything.
Where a re-export does work is when the mark is a layer rather than pixels. Export the timeline with the overlay hidden and the mark never gets composited; the same fixture puts one generation at 47.81 dB against a lossless render of the same timeline. That is the price of exporting at all, and it is the fix that costs nothing to try.
Because "watermark" searches land on metadata tools, it is worth separating the two layers with a measurement instead of an assurance. The same marked.mp4 was passed through this site's container cleaner:
freed /moov/udta/meta/ilst/(c)nam = "holiday clip" 36 bytes freed /moov/udta/meta/ilst/(c)ART = "phone editor" 36 bytes freed /moov/udta/meta/ilst/(c)too = Lavf63.1.101 36 bytes freed /moov/udta/meta/ilst/(c)cmt = "exported from a phone editor" 52 bytes file size 4,125,682 -> 4,125,682 bytes video payload 9acc851795c453a10a23b39b735e978c (unchanged)
Four tags out, and the picture byte-for-byte identical. An independent read with ffprobe confirms the same thing from outside our own code: before the clean the container reports title, artist, encoder and comment; after the clean, none of those four keys is present. What is genuinely useful about this layer is not the watermark story at all — it is the fact that an export carries a record of what it was called and which application wrote it.
Two disclosures. First, the fixture is built with ffmpeg, so the tags in it are ffmpeg's own. We cannot tell you what Clipchamp's exporter writes into its container, because that needs an account we do not have — read this as "what the layer is", not as "what Clipchamp writes". Second, this is the layer that has nothing to do with a statistical watermark. Anthropic's text watermark, for example, is a bias in how the model chose its tokens; its own documentation says "Nothing is added to the text and there are no hidden characters", so there is no byte in the file for any cleaner to remove. What that distinction means for a remover tool →
Free Clipchamp exports are capped at 1080p, and that matters to every repair option above. Measured on the fixture: a 1920x1080 frame is 2,073,600 pixels, and a corner mark of 320x90 is 28,800 pixels — 1.39% of the frame. Cropping the mark off means dropping the bottom 120 of 1,080 rows, which is 11.11% of the height. So the cheapest honest repair costs you about eight times more picture than the mark itself was occupying, and it shrinks the frame. If your source was 4K and you are exporting on the free plan, you already gave up three quarters of your pixels before you touched anything, which leaves a crop less headroom, not more.
If the mark turns out to be from a different editor, the layer logic is identical and this site has the same walkthrough for each: CapCut, InShot, YouCut, Premiere Pro. The general shape of the problem is on the three layers a video mark can live in, and the metadata layer has its own page: remove metadata from a video without re-encoding.
No, in Microsoft's own words. Its support page states: "Good news, the Clipchamp video editor does not add a visual, audio, or any other kind of watermark to your video editing projects or exported videos." The plans page says the same thing from the pricing side: the free plan includes "watermark-free video exports up to 1080p (full HD)". Premium features are 4K exports, premium stock media, premium filters and effects, and the brand kit. If you use one of those without the plan that covers it, the official page says "no watermark gets added but you will not be able to export and save your video until you upgrade" — an export block, not a stamp.
No, and there is nothing for one to remove. The free plan already exports without a watermark, so there is no mark to take off. When a premium asset is in the project, the official remedy is to replace the asset or upgrade the plan, because the block is on the export, not on the picture. A tool that claims to remove a Clipchamp watermark is either describing the preview hint you can already clear by swapping an asset, or selling you a generic video tool with a Clipchamp word in the title.
Find the layer first, because the answer changes completely by layer. If the mark is a text, sticker or logo layer on your timeline, delete it and export again: the footage track still holds the original frames, so the new export is clean and nothing has to be repaired — one generation, measured at 47.81 dB against a lossless render. If the mark is already burned into the only copy you have, you are in pixel territory: crop it off if it sits in a strip you can spare, or accept a patch that invents the pixels it covers. Exporting the file again does not help: measured on the fixture, the mark went from 26.49 dB to 26.48 dB.
Because the two are different things. Microsoft describes these as "small visual hints in the user interface to highlight the paid features that aren't included in your plan" — the editor draws them over its own preview so you know a premium asset is not licensed to you. That drawing never enters the exported file. If you can preview without the hint but not export at all, that is the documented behaviour: the export is blocked until the plan covers the asset. Remove the premium item, or license it, and both the hint and the block disappear together.
No. It is the single most repeated piece of advice on this subject and it is measurable. On a 1920x1080 fixture with a mark composited into the picture, one clean export scored 26.49 dB against a clean reference; encoding that marked file a second time scored 26.48 dB. Inside the mark's own rectangle the numbers were 7.9658 dB and 7.9656 dB. The mark is part of the picture, so re-encoding re-encodes the mark, and the only extra cost is a second generation of compression across the whole frame. Re-exporting removes a mark only when the mark is a layer you can delete before exporting.
You do not need one for that reason — Clipchamp's free plan already exports without a watermark up to 1080p, per Microsoft's own plans page. Switching editors does not remove a mark that is already inside your media either, because the mark is in the pixels and the next editor will faithfully re-encode those pixels. Switch if you want a different editing workflow, but do not expect a different editor to launder a mark out of your footage.
No. The free plan's exports are capped at 1080p (full HD); 4K exports are listed among the premium features available through qualifying Microsoft 365 subscriptions, alongside premium stock media, premium filters and effects, and the brand kit. That ceiling is worth knowing before you plan a repair: a 1080p frame is 2,073,600 pixels, so a corner mark occupying 28,800 pixels is 1.39% of the picture, while cropping it off costs the bottom 120 of 1,080 rows — 11.11% of the height.