Guide

Local image editor or an upload tool?

If the picture contains something you would not email to a stranger, do not upload it in order to hide it. A local editor changes pixels on your device. A cloud editor receives the file first. This page is that choice, not a ranking of brands.

Last updated

When does a local editor beat an upload tool?

Use a local editor when the image holds credentials, customer or patient information, government IDs, children’s faces, unreleased product UI, or anything you would not email to a company you do not have a contract with. Hiding those pixels should not require sending the file away first.

The awkward product is the one that says “upload your screenshot so we can blur the password.” You are handing over the thing you are afraid to hand over, to a server you will not see, under a privacy policy you will not read while you are in a hurry. Even a careful vendor then has a file, a backup, a log, and a breach story that is no longer only yours. If the redaction can happen on the machine that already has the image, that extra copy does not need to exist.

hideimage.com is one local option. The editor is a canvas in the page. Drop a JPG, PNG, or WebP, paste a screenshot, or choose a file. Draw boxes. Export a PNG. There is no account. The original file on disk is not modified. A desktop app you already trust — a photo viewer or an image editor installed on the computer — is also local. Use whichever one you will actually check before you send. The browser tool is there so you do not have to install something in the minute before a ticket is due.

Local also fits the social case, not only the corporate one. A plate on a car you are selling, a child’s face at the edge of a photo, a badge at a meetup: you can cover them without making an account on a photo host in order to borrow a blur tool. The limitation is the same in every local tool. You have to notice the sensitive region. Nothing here detects it for you.

What does “processed in the browser” actually mean?

It means the image is decoded and edited in the page you already opened, and the download is a new PNG of those pixels. It does not mean the site is offline. Page, analytics, and ad requests can still happen. Those requests are not the image. The privacy policy describes that split.

“No upload” is a claim about the picture, not a claim that your browser is offline. You loaded hideimage.com from Cloudflare. If analytics is enabled, a page view is measured. If AdSense is configured at build time, ad requests can run. None of that is a transfer of the bitmap you dropped on the canvas. If a tool cannot explain that distinction, be wary of the simpler slogan. This site’s privacy page is the place those requests are described.

The export is a new file. It is not the original JPEG with a sticker stored in a side channel. A black box in the PNG is black pixels. A blur is the mixed pixels, not a hidden original you can toggle. The camera or screenshot original remains on your device until you delete it or send it. People confuse those two files constantly. The local edit did its job and the share sheet undoes it. The guide on sharing safely is the second half of this one.

Because the PNG is newly drawn, the original photo’s EXIF — including GPS on a phone JPEG — is not copied into that download. That is a consequence of exporting canvas pixels, not a separate metadata product. Do not upload the original somewhere else just to strip location. Export after you have covered the visible secrets, and share the PNG.

What can a local browser editor not do?

It will not find faces or words for you, open a PDF, save a project, or certify a legal filing. Huge images depend on browser memory. It will not unsend a file you already uploaded. Collaboration and an official redaction process need more than this canvas. The canvas is the pixel step.

Automatic detection is the feature people expect and the feature this site refuses. Finding every face or every email would be convenient, and it is also the usual excuse to upload the image or to ship a heavier model with its own misses. You draw the rectangles. You will miss something if you rush. A checklist is the compensation: URL, sidebar, banners, names next to faces, plates, then a zoomed look at the export. An automatic tool that misses the sidebar has the same hole, plus a copy of the file.

There is no account, so there is no library of yesterday’s redactions and no one to email you a link. If you close the tab before you export, the in-memory image is gone. Export, then close. There is no copy-to-clipboard button. The download is the result. PDFs are not a format the canvas opens. Screenshot the page or export an image from the PDF viewer, then redact that image. If a filing has to be a redacted PDF with a particular method, follow that method. A black box here does not stamp a document as accepted.

Very large images can fail or stall because they have to fit in the browser. That is a limitation, not a silent upload. Resize a harmless copy if you must, or use a desktop editor on the same machine. Do not switch to an upload site only because the file is big, if the file is also sensitive. Big customer spreadsheets are exactly the files you should not send away in order to hide one column.

  • No automatic face detection, OCR, or “we found 12 secrets.”
  • No PDF editing. Redact an image or a screenshot of the page.
  • No saved projects and no account recovery of a picture.
  • No legal certification for a court, hospital, or employer policy.
  • No way to pull back an original you already uploaded or pasted into chat.

How do local, cloud, and desktop tools differ?

A local browser editor and a desktop app keep the image on your machine. A typical cloud editor receives an upload and may add accounts, auto-detect, and share links. Some desktop apps keep reversible layers. For a secret, export a flattened file you have looked at, and do not upload it.

Cloud editors earn their place when the picture is ordinary and the feature is the point: a team commenting on a crop, a batch of product photos, a filter you do not need for privacy. They are a poor place for the screenshot that contains a customer’s inbox or a production token. “The vendor is reputable” is not the same sentence as “I am allowed to give them this file.” If you cannot explain the upload to the person whose data is in the image, do not start it.

Desktop software is the option people forget. You already have it, it is local, and you might know it well. The risks are habit risks. A blur layer that is still a layer can be exported wrong. A crop tool might save over the original if you are not careful. A conversation screenshot pasted into a doc can be the original because you never exported. If you use a desktop app, export a flattened image, open that image, and read it. The same standard applies here.

This comparison is not a review of named products and it does not invent scores. Tools change, and a site that processes locally today should not be insulted by a page that never tested it. The durable distinction is the flow you can see: did the file have to leave before the sensitive pixels were destroyed? If the answer is yes, it is an upload tool, for this decision, even if the marketing says private.

What you are choosing
Local browser editorTypical cloud editorDesktop app on your computer
Where the edit runsIn the page you openedOn the vendor’s serverOn your computer
Does the image upload for editing?NoYesNo
AccountNot required hereOften requiredNot required
Finds faces or text for youNoSometimesSometimes
Best fitA secret you will not send awayA file you may already store thereA tool you already know how to export from
Main limitationYou mark every region yourselfThe file exists somewhere else firstEasy to save a layer or the original by mistake

How do you redact locally and then stop?

Paste the screenshot into the homepage editor, cover secrets with black boxes, cover faces and plates so they are not recognizable, and download the PNG. Open it. Attach that file. Do not upload the original afterward for a second opinion. A second tool that needs the original is a second copy of the leak.

A clean pass is short. Duplicate the screenshot if you might need the unredacted shot for yourself. Drop the copy on the editor. Black box tokens, passwords, ID numbers, and precise addresses. Pixelate or strongly blur faces and plates, and black out names beside them. Export. The strength and the mode apply to the next box you draw, so undo a weak box instead of stacking filters and hoping.

Then stop adding tools. The temptation is to run the result through another site “to be safe,” or to upload the original because the other site has auto-detect. You would be creating the copy local editing was meant to avoid, and auto-detect will still miss the sidebar. If you do not trust your own pass, use the checklist and look again. Ask a colleague to look at the redacted PNG, not at the original.

When the message is sent, the remaining copies are the ones on your machine. Delete the screenshot if you do not need it. Keep it if you do, somewhere that is not a shared drive named “public.” The editor cannot manage that folder. It can keep the redaction step from being an upload. Paste into the editor, export, and send the file you opened.

Questions about this

The useful questions are whether “upload” means the image leaves the device, what you give up by staying local, and whether another site that also says “local” has been reviewed here. This page does not score competitors. It tells you which kind of tool fits the picture in front of you.

Does hideimage.com upload the image to redact it?

No. You paste, drop, or choose a file. Blur, pixelate, and black box run in your browser. Export downloads a PNG. The site does not receive the picture for editing. Hosting, analytics, and ads, if ads are configured, are ordinary page requests and are described in the privacy policy. They are not an editing copy of your image.

Are other “no upload” websites reviewed here?

No. Several tools advertise local processing, and some editors genuinely do run in the browser. This page is not an audit or a ranking of them. If a site asks you to upload before you can draw, it is not local, whatever the headline says. Confirm the flow with a harmless image before you use it on a secret.

When is a cloud editor a reasonable choice?

When the image is not sensitive, when it already lives in that vendor’s account, or when your employer requires that vendor and you are allowed to send the file. Automation and collaboration are real features. They are a bad trade for a password, a medical image, or a customer record you are trying to hide.

Where should you go next?

Apply the cover in the same local editor this guide describes. Paste a screenshot on the homepage, or open a related note if the leak is a different kind. These links are the next step. They are not separate tools that upload the file.

Back to the editor