Skip to main content
AIDiveForge AIDiveForge
Visit Inpainty

Get This Tool

License: License: unverified

Share This Tool

Compare This Tool
📋 Embed this tool on your site

Copy this code to embed a compact tool card:

Inpainty

FreeOpen Source

Pricing

Model
Free

Summary

You screenshotted the wrong version of your UI, published it in your tutorial, and the only way to fix it was to redo the whole capture — Inpainty exists for that exact problem.

Upload a PNG, JPG, or WebP screenshot and the AI marks every detected text block as a clickable target. Tap a block, retype the text, download. The tool regenerates the image attempting to match the original font family, weight, size, and color. No account, no installation, no Photoshop license. The ceiling appears fast: single-block edits on clean screenshots work well, but complex backgrounds, decorative fonts, or tightly kerned text will produce mismatches the tool cannot recover from. When that happens, teams open Figma or Photoshop anyway.

Bottom line: Pick this to fix a published typo or swap UI copy into a second language in under two minutes — reach for a design tool the moment the background is complex or the font is anything other than a standard system face.

Community Performance Report Card

No community ratings yet. Be the first to rate this tool!

Best For: Quick text fixes in existing screenshots, Localization without redesign tools, Privacy-safe sharing of annotated images, Mobile-first screenshot editing, One-off edits without Photoshop

Community Benchmarks Community

No community benchmarks yet. Be the first to share a real-world data point.

  • No signup and no installation required, so a teammate who needs a one-time fix can be done before the time it takes to provision a Figma seat.
  • AI detects every text block independently and makes each one clickable, which means you do not have to mask or locate text regions manually the way you would in an image editor.
  • Format preservation per block — font family, weight, size, and color — so localized screenshots stay visually consistent with the source without manual style matching.
  • Mobile-first editing with native share sheet support on iOS and Android, so the fix-and-share loop does not require a desktop if the screenshot originated on a phone.
  • Text replacement doubles as content removal — typing nothing or replacement copy into a block hides names, prices, or emails, so sensitive screenshots can be shared without a separate redaction tool.
  • On decorative fonts, non-Latin scripts with complex rendering, or screenshots with photographic backgrounds, the regenerated text visibly mismatches the original — the vendor acknowledges this with 'tries to match' language, and there is no manual override for font or color. Teams with brand-critical assets open a design tool at that point.
  • There is no batch mode, no API, and no self-hosting path, so any team that needs to process more than a handful of screenshots — automated localization pipelines, QA screenshot diffing, documentation generation at scale — hits the tool's ceiling immediately and switches to a scripted solution or a design platform with programmatic export.

Community Reviews

No reviews yet. Be the first to share your experience.

About

Platforms
Web (browser), iOS, Android
API Available
No
Self-Hosted
No
Last Updated
2026-07-24T08:01:45.181Z

Best For

Who it's for

  • Quick text fixes in existing screenshots
  • Localization without redesign tools
  • Privacy-safe sharing of annotated images
  • Mobile-first screenshot editing
  • One-off edits without Photoshop

What it does well

  • Translate text in UI screenshots while preserving design
  • Correct typos in published tutorials or documentation
  • Anonymize sensitive information such as names or emails
  • Iterate on product mockups with updated copy
  • Edit chat or web-app screenshots on mobile

Discussion Community

No discussion yet. Sign in to start the conversation.

Spotted incorrect or missing data? Join our community of contributors.

Sign Up to Contribute

Community Notes & Tips Community

Be the first to contribute. General notes, observations, gotchas, and tips from people who use this tool day-to-day.

Frequently Asked Questions

Is Inpainty free?
Yes — Inpainty is fully free to use. There is no paid tier.
Is Inpainty open source?
Yes. Inpainty is open source.
What platforms does Inpainty support?
Inpainty is available on: Web (browser), iOS, Android.

Hours Saved & ROI Stories Community

Be the first to contribute. Concrete time/cost savings, with context. e.g. "Cut my code review backlog from 4h to 45m per week."

Inpainty

Fixing a screenshot after publication normally means re-running the entire capture flow or opening a layer-based editor most people do not have installed. Inpainty takes a different path: upload any PNG, JPG, or WebP up to 10 MB, and a vision AI model scans the image, marks every detected text block, and makes each one clickable. Tap a block, type the replacement text, hit Apply, and download. The vendor states the AI rebuilds the image preserving the original font, size, and color — no layer management, no selection masks.

The standout behavior is format preservation on standard screenshots. The AI targets font family, weight, size, and color for each block independently, so swapping English copy for a Spanish translation in a UI screenshot leaves the layout visually intact. The vendor also describes a mobile-first path: on iOS and Android the edited image can be saved directly through the native share sheet, which means the full edit-and-share cycle happens on the phone without a desktop detour.

The tool fits a narrow but real slot: one-off text corrections, localization of UI screenshots without reopening design files, and privacy-safe sharing where names, emails, or numbers need replacing before an image goes public. That slot has hard edges. The vendor notes the AI ‘tries to match’ typography — on decorative or non-standard fonts, or against complex photographic backgrounds, the regenerated text will diverge visually. There is no API, no self-hosting option, and no batch processing path, so teams with recurring automated screenshot pipelines will exhaust what this tool can do almost immediately and move to a scripted alternative.