Watermarking 4K and HDR Video Without Uploading It Anywhere

What "on-device" means in practice

It means the whole pipeline runs locally. Reel Brand reads the video from Photos or Files, composites your transparent PNG over each frame using Apple's Metal and Core Image frameworks, and writes a new file back to your device. The GPU doing that work is the one in your iPhone, iPad or Mac.

Nothing is staged on a server on the way through, which also means there is no upload queue, no render queue, and no waiting for a job to come back. The moment the export finishes, the file is already where you need it.

It also means the app does not need an account. There is nothing to sign into, because there is no remote resource to authenticate against.

Why 4K makes the upload path worse, not just slower

A 4K clip is roughly four times the pixel data of the same footage at 1080p, and modern iPhone footage is often HEVC at high bitrates. Upload time scales with that, and upload bandwidth is the half of most connections that was never fast to begin with.

But the round trip is only the visible cost. The less visible one is that a service which receives your video has to decode it, composite the overlay, and encode it again. That second encode is a generation of quality you did not ask to spend, applied to footage you already graded.

Processing locally skips both. There is no transfer, and there is no server-side re-encode in the middle of your pipeline.

HDR is where a re-encode actually shows

SDR footage survives a careless round trip reasonably well. HDR does not. Wide colour and high dynamic range carry information that a pipeline has to be built to preserve, and a service that treats every upload the same way will often flatten it — the highlights clip, the colour profile is replaced, and what comes back looks duller than what went in.

Reel Brand's exports keep the original colour profile and fidelity of SDR and HDR footage rather than flattening it, and audio is passed through bit-exact rather than re-encoded. The point of watermarking is to add one element to a video, and everything else about that video should come out the other side unchanged.

What this means if the footage is not yours

This is the case where the difference stops being technical. If you shoot for clients, footage under embargo, an unreleased product, or anything covered by an NDA, then "we upload it to process it" is a question you have to be able to answer.

When processing is local, the answer is short: the file never left the device. There is no copy on a server, no retention window to read, and no third-party subprocessor to name. That is a simpler thing to tell a client than any privacy policy.

Where iCloud does come in — and where it does not

One part of Reel Brand is synced, and it is worth being precise about which. With ReelBrand Pro Lifetime, the library of brand icons you have imported syncs across your devices so the same logos are available on iPhone, iPad and Mac. That sync runs through your own private iCloud container, under your Apple Account.

What syncs is the PNG icons you added. Video never enters it. If you turn the feature off, nothing syncs at all and the app works exactly as before.

The honest trade-offs

Local processing is not free of downsides, and a page that only listed the upsides would not be worth much.

Export speed is bounded by your hardware. A datacentre GPU farm will beat a phone at a large batch, and if you are processing a very long queue on an older device you will feel that. The available export resolutions also depend on the device and the source file — 4K is offered where both support it, not universally.

Long batches on a phone are also work the phone has to do, with the battery and thermal cost that implies. For a handful of clips this is invisible; for an afternoon of footage, a Mac is the better tool, which is why the Mac version exists.

What you get in exchange is that the footage stays yours, the quality is not spent on a round trip, and there is no subscription funding a server you are not using.