Learn · modules
What Is a Watermark Module in Minecraft?
A watermark module stamps a client's name or logo on screen for branding your clips. It's fully cosmetic: sends no data and can't be flagged by anticheat.
What is a Watermark Module in Minecraft?
A watermark, in a Minecraft utility client, is a small piece of branding, usually a name or logo, drawn onto a fixed spot on your screen while you play. It works the same way a watermark on a photo or a video does: it stamps the source onto whatever gets recorded, without touching the actual content underneath. As a module, watermark is a HUD element and nothing more. It doesn't move your character, doesn't read the world state, and doesn't send anything extra to the server. It exists so a clip circulating online, or a screenshot dropped in a Discord, is unmistakably tied to whatever client produced it.
The appeal is visibility without controversy. Every content creator wants their work to be recognizable. A watermark sits in the corner, completely transparent to gameplay, and handles that job. It's the gaming equivalent of a film studio's logo at the start of a movie: a credit, not a feature.
How it works
Watermark sits in the same family as any other HUD overlay: a coordinates readout, a potion timer, a keystroke display. The client renders a piece of text or a small logo image on top of the finished game frame, usually anchored to a corner (bottom right is the common default), after everything else on screen has already been drawn.
Game frame renders
Minecraft draws the world, entities, blocks, particles, everything normal.
HUD layer renders
Chat, hotbar, damage vignette, and other vanilla HUD elements draw on top.
Watermark draws
After all of that, a single text or logo element renders to a fixed position.
Frame complete
The finished image includes the watermark, and that's what recording software and screenshots capture.
Because it's a draw call and nothing else, it has no read access to anything that matters for gameplay: no player position, no block data, no entity list. It just paints pixels in the same place every frame. Most implementations expose a handful of controls—position or offset, size, and an on/off toggle—none of which touch a single outbound packet. That last detail is what makes the next section short.
Is it safe to use
Watermark is about as low-risk as a module gets. Anticheat, whether it's server-side detection on a competitive server or client-side integrity checks, works by inspecting what the client sends or how its behavior lines up with the game state: movement deltas, attack timing, packet sequencing. Watermark touches none of that. It's a local drawing operation with no network footprint and no interaction with game logic, so there's nothing for a detection system to compare against.
That puts it in the same bucket as other display-only modules: HUD customization, an FPS counter, a keystroke display, a digital clock. If a server ever banned someone over a logo in the corner of their screen, that would be a policy call, not a detection one. The watermark itself is always safe.
Watermark vs other visual modules
Watermark is part of a broader visual category built on the same instinct: surface information or branding without touching anything a server-side check would care about. Unlike a lighting override or an XRay module, a watermark adds zero information about the world and changes zero game state.
| Visual Module | What it does | Server concern |
|---|---|---|
| Watermark | Draws a logo on screen | None |
| Ambience | Changes world lighting | None |
| Coordinates HUD | Displays player position | None |
| XRay | Reveals ore through blocks | High |
Watermark is at the safe end, where coordinates HUD and ambience sit. XRay is in a different conversation entirely.
FAQ
No. It only draws text or a logo on screen and has zero connection to movement, combat, or anything the server processes.
No. It never sends anything to the server, so there's nothing for a server-side anticheat to observe about a purely local overlay.
Mostly branding and identification: it makes clips and screenshots recognizable, and lets you confirm at a glance which client, or which build, you're running.
Usually, yes. Most implementations let you reposition it, resize it, or disable it outright, though the exact controls depend on the client.