Website profiles · Technology insights · Alternatives

redacted.app

Blur faces, censor text, black out IDs, and redact images right in your browser. AI finds faces automatically — nothing is uploaded. Free, no account.

No paid content found Multilingual
Visit website
Profile views 15 Outbound visits 19 Normal
Redacted Full homepage screenshot

At a glance

Category
Artificial Intelligence
Language
English
Paid-content signal
No paid content foundObserved
Registered
2019
Hosting
CloudflareInferred
HTTPS certificate trusted
PassedObserved
Last updated

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is Redacted?

Redacted is a browser-based image redaction tool. You drop or paste a photo or screenshot, and it blurs faces, blacks out text, or covers details like ID numbers — all locally on your device. Nothing is uploaded, there's no account, and it's free.

What it does

  • Automatic face detection: AI finds every face in an image so you can hide them in one click.
  • Manual redaction: Blur, pixelate, or black out anything the AI misses — text, license plates, addresses, tattoos.
  • Metadata stripping: Exported images have their metadata removed automatically, including GPS/location data.
  • No upload, works offline: Processing runs in your browser, so sensitive documents and family photos never touch a server.
  • Formats: JPEG, PNG, GIF, and WebP.
  • Platforms: Works in desktop and mobile browsers; native Mac and iOS apps exist for offline use and batch folder processing.

Who it's for

Anyone sharing images that contain private information: people posting portraits who want faces obscured, parents covering kids' faces in family photos, or anyone posting a photo of an ID, bill, or document that needs details hidden before it goes public.

Trade-offs to weigh

Browser-based redaction is convenient and private, but it's manual-ish work — you still review the result, because automated face detection can miss profiles, partially hidden faces, or faces in reflections. For one-off images, the web version is the fastest path. If you're redacting many files repeatedly, a native app with batch processing is the more practical choice.

A concrete next step

If you have a screenshot with an account number or address visible, paste it into Redacted, let the AI flag faces, then manually black out the text fields and download. Check the exported file at full zoom to confirm nothing sensitive remains before sharing.

How does Redacted's on-device AI automatically find faces and text in my images?

Redacted uses on-device AI to scan your image for faces and text as soon as you add it, then lets you hide what it finds with a click. The processing happens in your browser or in the native Mac/iOS app, so the image itself is not sent to a server for analysis.

H3 What "on-device" means in practice

  • In the browser: the detection model runs locally in your browser tab. Redacted's page states nothing is uploaded and the tool works offline.
  • In the native Mac and iOS apps: the same local-AI approach is used, with the Mac app adding batch workflows for whole folders.
  • The practical trade-off: you get privacy and offline use, but detection quality and speed depend on your device rather than a large cloud model. Very large images or older phones may take longer.

H3 Typical workflow

  1. Drop or paste an image, or pick a sample.
  2. Redacted highlights detected faces automatically; text detection is also part of its on-device AI.
  3. You apply a redaction style — the page shows pixelation, emoji covers, and black bars as examples.
  4. Download the result. The page says exported images have metadata, including GPS/location data, stripped automatically.

H3 A concrete scenario You photograph a passport or a child's school form and want to post it in a group chat. Instead of manually drawing boxes over every name and face, you drop the image in, let the AI mark the faces and text regions, then adjust or confirm the redactions before exporting. This is faster than manual blurring and reduces the chance of missing a detail.

H3 Choosing between browser and app

  • Use the browser tool for one-off images on any device, including mobile.
  • Use the Mac or iOS app if you need offline-first work, batch processing of folders, or prefer a native interface.
  • Both share the same core promise: local AI detection, no account required.

For a quick test, try the sample image on the site first to see how accurately it detects faces and text in a photo similar to yours. If detection misses something important, plan to review and add manual redactions rather than relying on automation alone.

Can I redact photos on my phone or do I need to install the Mac app?

You can redact photos on your phone — no Mac app required. Redacted runs in a mobile browser, so you can open it on your phone, drop or paste an image, and redact it there. The Mac app is an optional extra, not a prerequisite.

What the browser version does

  • Works on desktop and mobile browsers.
  • AI finds faces automatically; you can also blur, black out or pixelate details manually.
  • Opens JPEG, PNG, GIF and WebP files.
  • Exported images have metadata, including GPS/location data, stripped automatically.
  • No account, and the page states images are processed on your device rather than uploaded.

H3. When the Mac app makes more sense The native Mac app is aimed at people who want offline use, batch processing of whole folders, and the same on-device AI detection. If you are redacting one or two screenshots on the go, the browser is the faster route. If you are clearing a folder of family photos or work documents, a desktop batch workflow saves repeated manual steps.

A practical phone workflow

  1. Open Redacted in your phone browser.
  2. Paste or select the photo — screenshots from your camera roll work fine.
  3. Let the AI mark faces, then add manual blocks over text, ID numbers or addresses.
  4. Download the redacted copy and share that version, keeping the original unedited.

One caveat: redaction is only as good as your review. Zoom in before sharing, because small text or a partially covered face can survive a quick blur. If you want a second opinion on the approach, Redacted itself shows before-and-after examples for portraits, family photos and IDs.

What happens to the GPS and metadata in my images after I redact them?

Redacted says exported images have their metadata, including GPS/location data, stripped automatically. So when you redact a photo and download the result, the location tag and other embedded metadata are removed as part of the export — you don't have to run a separate cleanup step.

That matters most in a few common cases:

  • Photos taken on a phone and shared publicly. Camera apps often embed GPS coordinates, so a picture of your street or a child's school can reveal where it was taken even after faces are blurred.
  • Screenshots of documents or receipts. Metadata can carry device and app details you'd rather not hand over.
  • Anything posted to a marketplace, forum or dating profile. Location data is the detail people forget, because it's invisible in the image itself.

A useful next step: after downloading a redacted image, check the exported file's properties (on macOS, Get Info; on Windows, right-click → Properties → Details) and confirm the GPS field is empty. That takes a few seconds and verifies the cleanup on the specific file you're about to share, rather than trusting it in general.

One caveat worth understanding: stripping metadata removes hidden information, but it doesn't undo what's visible in the pixels. A street sign, a house number, a distinctive landmark or a reflection in a window can still identify a place. If location privacy is the real goal, redact those visible cues too — and remember that a blur or pixelation is only as strong as the area you cover.

If you want a second tool to cross-check metadata removal, ExifTool is a long-standing command-line utility for reading and writing image metadata, and Verexif is a browser-based option that displays and removes EXIF data.

Which image file formats can I open and redact in Redacted?

Redacted accepts four image formats: JPEG, PNG, GIF, and WebP. That covers the common cases — phone photos (JPEG), screenshots (PNG), web images (WebP), and simple graphics or short animations (GIF).

A few practical notes drawn from what the site states:

  • JPEG and PNG are the ones you'll use most: photos and screenshots respectively. Both work well for face blurring and text blackouts.
  • WebP is worth knowing about because many images saved from websites or messaging apps arrive in this format, and not every redaction tool opens it.
  • GIF support is listed, but if you're redacting an animated GIF, expect the redaction to apply to the image you see rather than being a specialized frame-by-frame animation editor — for anything beyond a static frame, test the export before relying on it.
  • Exported files come back with metadata, including GPS/location data, stripped automatically — useful when you're sharing a photo taken on a phone.

Next step: if your file won't open, it's likely a format outside this list — HEIC from an iPhone camera roll is the usual culprit, and the fix is to convert it to JPEG first. If you're working with a whole folder of images rather than one at a time, the site points to its Mac app for batch workflows, while the browser version handles single images with no install or account.

For a broader set of image tools, you can also compare with Squoosh for format conversion before redacting.

How do I batch redact an entire folder of photos offline on Mac?

Batch redaction of a whole folder is a desktop-app job, not a browser job. The browser version of Redacted handles one image at a time — drop or paste it, redact, download. The Mac app is the one described as doing batch workflows, with on-device AI finding faces and text and nothing leaving your machine, so it fits an offline folder-at-a-time routine.

A practical workflow on Mac:

  1. Install the native app from the App Store, then disconnect from Wi-Fi or turn off networking to confirm it still works — offline operation is the point.
  2. Copy the folder you want to process to a working directory rather than editing originals in place.
  3. Point the app at the folder and let its face and text detection mark candidates.
  4. Review every auto-detection before exporting. Detection is a first pass, not a guarantee: profile faces, faces in shadow, small background faces, and stylized text are the usual misses, and you should add manual boxes for anything the AI skipped.
  5. Export to a separate output folder so you keep an untouched original set.
  6. Spot-check a few exports at full size to confirm the redaction is opaque or blurred enough, and that metadata has been stripped.

Two trade-offs worth knowing. Automatic detection saves the most time on large batches of similar photos (event photos, ID scans, screenshots), but it saves the least on unusual images, where manual review dominates. And blur is a weaker redaction than a solid block for text — blur can sometimes be partially reversed; black boxes or pixelation are safer for IDs, account numbers, and addresses.

If you only have a handful of images and no Mac app, the browser tool covers it: it works offline in the browser, needs no account, and strips metadata including GPS on export. For a wider look at the tool itself, see Redacted.

Related questions

More questions →
How to Compress Images for the Web Without Losing Visible Quality

You can cut most images to a fraction of their original file size without any visible quality loss by doing three things in the right order: resize the image to the dimensions it will actually display at, pick the right format for the content, then apply compression at a quality level that survives a side-by-side check. The single biggest mistake is skipping step one — an oversized image compressed at maximum quality is still far heavier than a correctly sized one.

Why file size and quality are a trade-off, not a fixed setting

Every compressed image is a negotiation between three variables: how many pixels you keep, how precisely each pixel is described, and how much the format is allowed to guess.

  • Dimensions decide how many pixels exist at all. Halving width and height removes 75% of the pixel data before any compression happens.
  • Quality level decides how aggressively the encoder discards detail it thinks you won't notice.
  • Format decides the kind of discarding allowed — some formats throw away color precision, others only remove redundancy.

Because these interact, "quality 80" means something different on a 4000px photo than on a 600px thumbnail. Tune dimensions first, then quality.

Pick the format before you touch the quality slider

Format Best for Compression type Transparency Notes
JPEG Photographs, gradients, complex scenes Lossy No Smallest for photos; artifacts appear around sharp edges and text
PNG Logos, icons, screenshots, flat color, anything needing transparency Lossless (or lossy via quantization) Yes Often 5–10× larger than JPEG for photos; excellent for flat graphics
WEBP Almost everything, as a modern default Both lossy and lossless Yes Typically 25–35% smaller than JPEG at comparable quality; broad browser support
SVG Logos, icons, diagrams, charts Vector (resolution-independent) Yes Stays crisp at any size; not suitable for photos
GIF Short simple animations only Lossless, 256 colors Yes (1-bit) Superseded by WEBP/MP4 for animation in nearly all cases

Practical rule: photos → JPEG or lossy WEBP; flat graphics and transparency → PNG or lossless WEBP; anything vector → SVG.

The four levers, in the order you should pull them

1. Resize to display size (biggest win, zero quality cost)

If your layout renders an image at 800px wide, serving a 2400px original wastes roughly 89% of the pixels. Resize to the largest size it will ever be displayed at, and add a 2× version only if you need retina sharpness.

2. Choose the format

Match the format to the content type using the table above. Converting a photographic PNG to JPEG or WEBP alone can shrink it by 80% or more.

3. Set the quality level

For JPEG and lossy WEBP, most photographs hold up well between quality 70 and 85. Below ~60, banding appears in skies and blur around text. Above ~90, file size climbs steeply for gains nobody can see.

4. Strip metadata

EXIF data, camera info, and embedded thumbnails can add tens of kilobytes. Remove them unless you specifically need copyright or orientation data — and note that stripping orientation can rotate an image, so verify after export.

When lossy compression is fine, and when it isn't

Lossy is acceptable when:

  • The image is a photograph or has natural texture.
  • It's decorative or below the fold.
  • Slight softening won't be noticed at final display size.

Use lossless or vector instead when:

  • The image contains text, UI elements, or thin lines (lossy creates ringing artifacts).
  • It's a logo, icon, or diagram — SVG or PNG keeps edges clean.
  • It will be edited again later; repeated lossy saves compound degradation.
  • It's a screenshot of code or a chart where color accuracy matters.

Compressing vs. resizing: don't confuse them

Compressing reduces the bytes needed to describe the same pixels. Resizing reduces the number of pixels. They're independent, and resizing usually delivers the larger saving. A 3000×2000 photo at quality 95 might be 2 MB; the same photo resized to 1200×800 at quality 80 might be 180 KB. Doing only the quality reduction gets you maybe 40% off; doing both gets you over 90%.

A repeatable workflow

  1. Determine the maximum display width in your layout (inspect the element or check your CSS).
  2. Export at that width (plus a 2× variant if needed).
  3. Convert to the right format — WEBP as a modern default, JPEG as a fallback, PNG/SVG for graphics.
  4. Apply quality 75–85 for lossy formats and compare against the original.
  5. Strip metadata and re-check orientation.
  6. Verify before publishing (see below).
  7. Serve the right file with srcset so small screens don't download the large variant.

How to verify quality before you publish

  • View at 100% at final display size, not zoomed in — artifacts you can't see at real size don't matter.
  • Toggle between original and compressed in a viewer or an online compressor's before/after preview.
  • Check the worst-case areas: skies, smooth gradients, sharp edges, and any text.
  • Compare file sizes and ask whether the extra kilobytes buy visible improvement. If not, go smaller.
  • Test on a mid-range phone, where banding and blur are often more obvious than on a desktop monitor.

Common mistakes

  • Compressing a full-resolution image and calling it optimized.
  • Using PNG for photographs.
  • Setting quality to 100 "to be safe" — it inflates size with no visible benefit.
  • Re-saving a JPEG repeatedly, stacking artifacts each time.
  • Forgetting that GIF animations are usually better as WEBP or video.
  • Ignoring metadata, which can silently add weight.

Quick reference

Goal Do this
Photo on a webpage Resize to display width → WEBP (fallback JPEG) → quality 75–85
Logo or icon SVG; fall back to PNG if vector isn't possible
Screenshot with text PNG or lossless WEBP
Transparent photo cutout Lossy WEBP or PNG
Short animation WEBP or MP4, not GIF

The order matters more than any single setting: resize, then choose format, then tune quality, then strip metadata, then verify at real display size. Follow that sequence and you'll routinely land at 10–20% of the original file size with no quality your visitors can detect.

Website Overview

An established domain and managed infrastructure suggest continuity of operations and may support dependable delivery, although neither guarantees service quality. Page metadata, canonical configuration and social previews work together to provide more consistent search and sharing presentation.

Domain and Registration

Registered in 2019, this domain has about 6 years of history. That suggests continuity, although ownership and purpose may have changed. Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The registrar is CloudFlare, Inc., a widely used domain service provider. The domain uses the common .app extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by Cloudflare, indicating managed DNS hosting. MX records point to the Cloudflare Email Routing email service. No CNAME was found; the observed records resolve directly to addresses. SPF and DMARC are configured. DKIM status is unknown. TXT records include verification markers for Google. Such markers may also remain after a service stops being used.

TLS and Certificates

The public key uses EC with 256 bits. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued within the Google Trust Services cloud or CDN ecosystem. The certificate's total validity is about 90 days, consistent with a short renewal cycle.

HTTP and Browser Security

The response lacks these common security headers: CSP. CORS permits any origin to read this response. This is common for public resources; sensitive responses need narrower handling. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. The cf-ray response header indicates a CDN or caching proxy in the delivery path. No obvious internal addresses or debug information were found in the headers.

Technology Stack Analysis

The public page identifies Cloudflare without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

Twitter Card metadata is configured. JSON-LD includes Organization data, helping describe the organization as an entity. The page declares 3 language or regional alternatives using hreflang. The title has 52 characters, within a common display range. A meta description is present, with 150 characters.

Hosting and Email

DNSCloudflare
HostingCloudflare
EmailCloudflare Email Routing
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) Location unknown Inferred 104.21.69.127

Registration details

RDAP / WHOIS

RegistrarCloudFlare, Inc.
Registered2019-12-02
Expires2026-12-02
Domain statusclient transfer prohibited
Nameserversdamon.ns.cloudflare.com、zoe.ns.cloudflare.com
DNSSECunsigned

DNS records

DNS

TypeNameValueTTLPriority
Aredacted.app104.21.69.127300—
Aredacted.app172.67.208.178300—
AAAAredacted.app2606:4700:3033::ac43:d0b2300—
AAAAredacted.app2606:4700:3035::6815:457f300—
MXredacted.approute1.mx.cloudflare.net3008
MXredacted.approute2.mx.cloudflare.net30047
MXredacted.approute3.mx.cloudflare.net30090
NSredacted.appdamon.ns.cloudflare.com86400—
NSredacted.appzoe.ns.cloudflare.com86400—
TXTredacted.appgoogle-site-verification=bfidXePjWZ8fB-AWfMftWwFcP5osudqfC-sPHMZ8Aig300—
TXTredacted.appv=spf1 include:_spf.mx.cloudflare.net ~all300—
DMARC_dmarc.redacted.appv=DMARC1; p=reject;300—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectredacted.app
IssuerGoogle Trust Services
Valid until2026-12-11T17:22 · Remaining when checked: 70 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=utf-8
cache-controlpublic, max-age=0, must-revalidate
servercloudflare
strict-transport-securitymax-age=15552000
x-frame-optionsSAMEORIGIN
x-content-type-optionsnosniff
referrer-policysame-origin
permissions-policycamera=(), microphone=(), geolocation=(), browsing-topics=()
access-control-allow-origin*

Identified technologies

Cloudflare

Pages, Search and Sharing

Meta descriptionBlur faces, censor text, black out IDs, and redact images right in your browser. AI finds faces automatically — nothing is uploaded. Free, no account.
Canonical URLhttps://redacted.app/
LanguageEnglish (default) · Multilingual
Twitter Cardsummary_large_image
All bots 1 allowed · 0 disallowed
  • Allow/

User reviews (0)

  • No reviews yet.