Why Mandumon Tools Process Everything in Your Browser

When you use an online converter, it is fair to wonder where your photo goes. Mandumon's Emoji Maker and Design QR are built so that the text and images you enter are handled inside your own browser rather than uploaded to a server. This article explains how that works, what it improves, and what it makes harder, without glossing over the trade-offs.

What "processed in your browser" means

A typical online tool sends your file to a server, which converts it and sends back the result. Browser-side processing works differently. When the page opens, a program written in JavaScript arrives with it, and every later calculation runs on your own computer or phone. When you pick a photo, the file is read into the browser's memory and drawn there; it does not leave your device. The server's job is to deliver the page and the program. It never receives your picture.

Why we built it this way

• Privacy. A family photo, a company logo, or a Wi-Fi password inside a QR code never has to travel anywhere, so there is nothing to entrust to us.
• Speed. There is no upload and download to wait for, so the preview changes the moment you edit the text.
• Cost and durability. Without conversion servers to run, the tools can stay free with no sign-up or subscription, and there is less that can go down.
• Resilience. Once the page has loaded, most work can continue even on an unreliable connection.

Canvas and Web Workers in plain language

Browsers include a drawing surface called Canvas. You tell it where to place text, in which font, or how many degrees to rotate a photo, and it produces the picture pixel by pixel. An animated emoji is simply many slightly different pictures drawn one after another and stitched into a sequence. Packing those frames into a single GIF file, called encoding, also happens in the browser.

A Web Worker is a helper that lets the browser run calculations separately from the work of keeping the screen responsive. If heavy math runs in the same place as the interface, buttons can freeze; handing it to a worker keeps things smooth. Not every tool needs one, but this is part of why browser-side processing is practical today: the browser already ships with these capabilities.

The honest limits

Processing in the browser is not magic. It helps to know where it falls short.

• Your device matters. Large images or GIFs with many frames can be slow, or fail, on an older phone.
• Some data is downloaded the first time. Fonts and features such as AI cutout fetch what they need on first use. That means downloading a font or model, not sending your photo.
• Nothing is entirely invisible. Basic access records such as the address requested, time and browser details may be handled by the hosting provider, Cloudflare, and design settings like colors can be remembered in your own browser.
• Sharing is different. If you choose to publish an emoji to a gallery, the information needed to show it is stored on a server. Emoji that use an uploaded image cannot be published.
• You can verify it yourself. Anyone comfortable with browser developer tools can watch the Network tab. Being checkable matters more than being told to trust us.

How to check it yourself

1. Open Emoji Maker in your browser, then open developer tools (F12) and go to the Network tab.
2. Upload a photo and change a few effects while watching the tab.
3. You will not see an upload request (POST) carrying your image.