What a watermark can and cannot do
A watermark will not stop a determined thief from cropping it out or screenshotting around it. What it reliably does is mark proofs as unfinished, remind a casual viewer who made the frame, and keep a brand mark attached when images travel through chat apps, screenshots, and social media re-shares long after the original post is forgotten. Photographers and brands need slightly different defaults, but both can watermark online without installing a desktop plugin or learning layer masks.
Logo marks vs text marks
Logo watermarks
Logo watermarks suit finished marketing images and anything going out under a brand kit. The logo has to stay legible at small display sizes - a detailed emblem rasterized down to 40 pixels wide often turns into a muddy smear that helps nobody and just adds visual noise to the corner of an otherwise clean photo.
Text watermarks
Text watermarks suit copyright lines, studio URLs, photographer names, and large diagonal PROOF labels across a selection gallery. They are faster to restyle per client or per shoot, since changing a name or date is a text edit rather than a logo swap.
Placement that still respects the photo
- Bottom-right or bottom-left corners for subtle branding on finished, delivered images
- Larger centered translucent text for client proof and selection galleries, where visibility matters more than subtlety
- Avoid covering faces, product details, or chart data no matter which placement style you choose
Opacity is ultimately a taste call, but the target is consistent: readable on a phone screen at normal brightness, not a sticker plastered over the subject that makes the photo hard to actually evaluate.
Watermark a photo on Picnie
- Go to Watermark Images
- Upload your photo
- Choose logo or text, then set position, size, and opacity
- Preview on a detailed frame - hair, jewelry, or small type reveal placement problems that a plain background never will
- Download the result
Proof workflow vs final delivery
Send strong, hard-to-remove PROOF marks while clients are still choosing favorites from a gallery. After approval and payment, deliver clean files, or a light corner brand mark if that is what your contract specifies. Never keep proof-marked and final-marked files mixed together in one shared drive folder without clear labeling - a client downloading the wrong version, watermark and all, is an avoidable and awkward conversation.
Setting a default that survives a busy season
Wedding and event photographers in particular tend to reuse the exact same watermark style across an entire season of bookings. Decide the position, opacity, and text or logo choice once, write it down somewhere you will actually check, and apply it identically to every gallery rather than eyeballing placement fresh for each new shoot. Consistency here reads as professionalism to clients even when they never consciously notice it.
Scaling past a single photo
For whole galleries, use batch watermark with the exact same settings you already approved on a single hero image, rather than re-deciding placement and opacity for every new upload.
Watermarking for print vs watermarking for screens
A watermark tuned for a screen preview can behave differently once a client actually prints a proof at home or at a local lab. Light, semi-transparent text that reads clearly on a backlit monitor can wash out almost completely on a matte print, or conversely turn into a heavy gray block on glossy paper under certain lighting. If proofs are likely to be printed rather than only viewed on a phone or laptop, test the watermark on an actual printed sample before finalizing opacity - a setting that looked perfect on screen is not automatically the right setting once ink and paper are involved.
Handling client requests to remove a watermark early
Clients will occasionally ask for an unwatermarked copy of a photo they have not yet paid for or been formally delivered - sometimes innocently, sometimes to sidestep the payment step entirely. Having a default policy decided in advance, rather than improvising an answer in the moment, avoids awkward back-and-forth: deliver final files only after payment or approval clears, and keep that rule the same for every client rather than making case-by-case exceptions that are hard to justify consistently later.
Picnie at Picnie. Writes about image automation, developer experience, and shipping product faster.