About this tool
Add text watermarks to images in your browser
Mark photos before posting on social, sending to clients, or sharing publicly. A clear watermark deters unauthorized reuse and makes attribution explicit. Everything runs locally. Your image never leaves your device.
Why use OmegaPix
-
Discourages unauthorized reuse : A visible watermark signals ownership. People who would casually re-post your unmarked photo think twice when their crop or repost still shows your handle or copyright line.
-
No upload, no account : The watermark is drawn onto your image in your browser via Canvas. Open DevTools → Network during the operation and you will see zero outbound requests carrying image bytes.
-
Pixel-perfect output : PNG and WebP outputs are lossless. JPG output uses your chosen quality (default 92). The watermark is anti-aliased and renders crisply at any size.
How it works
Drop your image
JPG, PNG, WebP, or AVIF. Up to 50 MB on desktop.
Type your watermark
Your handle, copyright line, or studio name. Pick a corner, opacity, font size, and color.
Download the marked copy
Save as JPG, PNG, or WebP. Original image stays in your downloads untouched, the watermark only applies to the export.
Frequently asked questions
Is the watermark permanent?
Yes. The text is painted directly onto the pixel data of the exported file. There is no separate layer that a viewer can disable, and no metadata flag indicating the file was watermarked. To a downstream viewer, the watermark looks like part of the original photograph.
Can I add a logo or image watermark?
V1 supports text only. Image/logo watermarking is on the roadmap for a future release. For now, you can use any short text, your domain, an @handle, a copyright symbol followed by your name, that fits in a single line.
Does the original image change?
No. Your source file on disk is untouched. The watermarker reads it into the browser, draws the watermark onto an in-memory canvas, and exports a new file. The original stays exactly as it was.
Where should I position the watermark?
Bottom-right and bottom-left corners are the social-media standard, visible but unobtrusive. Center positioning is for stronger anti-reuse signaling (harder to crop out, but more visually intrusive). Top corners work well when the image has a busy bottom edge.
What opacity should I use?
60-80% works for most photos, visible but not dominant. Drop to 30-40% for delicate compositions where the watermark should whisper rather than shout. Push to 90-100% only if anti-reuse signaling is the highest priority and visual impact is acceptable.
Will the watermark survive social-media compression?
Yes, for normal use. Instagram, Twitter/X, and Facebook recompress every upload, but the recompression preserves visible structure. Your watermark text remains readable. Very small font sizes (under 12px in the rendered output) may blur on aggressive recompression, use 16px or larger for safety.
Does the watermarker work with transparent PNGs?
Yes. Transparency is preserved on PNG and WebP output. The watermark is composited on top of whatever is already there; if your image has alpha, the alpha stays.
Can I batch-watermark multiple images?
V1 is single-image. Batch mode is on the roadmap. For now, repeat the workflow per image. The controls remember your most recent settings during the session.
When to use this tool
Photographers sending proofs
Mark client review proofs with your studio name + "PROOF" so they cannot be circulated unfinished.
Designers sharing concept work
Mark unapproved mockups before sending to multiple stakeholders. Concept leaks happen, make sure your name travels with the file.
Creators sharing on social
Add your @handle to images before posting. When someone screen-grabs and reposts without credit, your handle still travels with the pixels.
Documentary photographers
Stamp date/location into the image edge for chain-of-custody on field photos.
When not to use this tool
You need a removable watermark
There is no such thing in standard image formats. Watermarks are part of the pixel data. If you need a "preview" version that you can later "unlock", use a separate file naming convention instead.
You need batch processing today
V1 is single-image only. If you have hundreds of images to mark, wait for batch mode or use a desktop tool like ImageMagick from the command line.
The image will be heavily cropped after sharing
A corner watermark gets cropped away. For images you expect to be screenshotted and cropped, center positioning survives, accept the visual cost.
Technical details
How the watermark is rendered
The image loads into a hidden <canvas> at its full natural resolution. The watermark text is drawn using the canvas 2D API with anti-aliased font rendering. Position is computed from a 9-cell grid (top-left through bottom-right plus center). Opacity is applied via the canvas globalAlpha property. The watermarked canvas is then exported via toBlob() at your chosen format and quality.
Why corner positioning is standard
Corner positioning trades anti-reuse strength for visual intrusion. Bottom-right is the photography industry default, visible to anyone reading the image left-to-right, top-to-bottom, but small enough not to dominate the composition. Center positioning is "hostile" watermarking, used when the image is unfinished or licensed for preview only.
Output formats
JPG: smallest file size, lossy, perfect for photos. Quality slider runs 60-100; default 92 is the social-media sweet spot. PNG: lossless, preserves transparency, larger files (typically 2-4x). WebP: ~30% smaller than JPG at equivalent quality, lossless or lossy. Pick PNG for logos and screenshots; JPG or WebP for photos.
Font sizing rule of thumb
Watermark height should be roughly 1-2% of the image height for unobtrusive marking, 3-5% for stronger signaling. A 1920×1080 image with a 24px watermark reads as confident attribution; a 48px watermark reads as a copyright assertion. The tool scales font size proportionally to the image so the on-screen preview matches the exported file.
What gets preserved
EXIF and metadata: your choice. By default the watermarker preserves the source metadata (the export contains the same EXIF, GPS, ICC profile, etc. as the input). If you want a watermarked AND metadata-clean output, run the result through the EXIF Remover after.
Your files stay on your device
The watermark renders entirely in your browser. The image file is read locally via the File API, processed on a Canvas element, and exported via canvas.toBlob. No upload, no server processing, no third party touches your image. Verify with DevTools → Network during the operation.