Edit text in a screenshot

Use this editor for your own app screens and design examples: update a button label, correct an onboarding headline or revise a sample value after the screenshot was exported.

A PNG capture usually preserves fine interface text better than a compressed JPG. Enter one UI element per line, then compare icons, spacing and the status bar before using the image.

If you can open the product or design file, taking a fresh screenshot provides the most exact result. Image editing is useful when you only have the exported capture or need a quick mockup.

Do not alter messages, payments, account records or other screenshots to misrepresent what happened. The acceptable use policy explains the prohibited cases.

Screenshots saved as PNG tend to keep sharp edges on small UI type. JPEG screenshots can show compression around letters, especially after being shared through a messaging app. Upload the cleanest source under 10 MB.

Replace one UI element per text pair. Longer labels may not fit their buttons, and small icons or status information can drift; zoom in before publishing the result.

If you have the app, browser state or design file, making the change there and taking a new capture gives you precise control. An image editor is useful for a flat export when the source is unavailable or a quick concept is enough.

App-store screenshots and documentation should accurately represent the product. Editing private messages, receipts or account balances to imply an event happened is prohibited.

A product screenshot may need a new button label, a corrected feature name or a revised heading after a copy review. Start with your own app capture or an authorized mockup, then enter the exact existing UI text and the new wording. The screenshot remains an image rather than becoming an editable interface.

For a help article or store listing, the image should faithfully describe the current product. If the original application is available and can be opened in the correct state, capturing the real screen again is the most precise option. Image editing is useful when a flat export is the practical starting point.

Screenshots from phones and browsers contain small type, icons and interface chrome. A clean PNG capture preserves sharp edges; a JPEG may already contain compression artifacts around letters. Upload one PNG, JPG or WebP no larger than 10 MB and avoid upscaling a tiny screenshot before the edit unless necessary.

After the result is ready, inspect the status bar, navigation, buttons and text outside the edited area. The model aims to preserve those details, but it does not promise pixel-identical output. The original and generated image can also have different pixel dimensions.

An app-store image has two jobs: it must show the product accurately and meet the store's technical specifications. An edited screenshot can help draft a new caption, but compare it with the actual product and check the downloaded file's width, height and format before uploading.

If you are preparing translated images, verify terminology and whether the app truly supports that language. Use the linked Apple screenshot specifications for current supported sizes, and consult the destination platform's own rules rather than assuming one resolution works everywhere.

Use Replace text when you have a specific old label and replacement. Add a separate pair for each UI element and keep new labels short enough to fit their buttons. This is a useful way to explore wording in an honest product mockup.

Use Translate when the goal is a new-language image. Choose one target language for each submission and ask a fluent speaker to review the result. For a localized product that can be run directly, a fresh capture of the actual localized interface remains the strongest reference.

Do not alter conversations, financial records, account balances or payment screenshots to suggest something happened when it did not. A mockup of your own interface and a falsified record are different use cases; the latter is prohibited by the acceptable-use policy.

When showing an edited design to colleagues, identify it as a proposed or illustrative version if it does not represent the live interface. This prevents a design review image from being confused with evidence of a real transaction or statement.

A documentation screenshot can become stale when an application changes a navigation label or headline. Identify the old wording exactly, then replace it with the wording actually used by the product. If an interface also changed its layout or functionality, recapture the updated application instead of editing only the words.

After the edit, review any arrow, callout or surrounding label in the help article. A screenshot can be visually polished and still be wrong for the documented workflow. Give readers the same button names and steps they will see in the real application.

Phone screenshots may include a status bar, clock, battery indicator, navigation controls and tiny system text. Desktop captures may show browser chrome or window controls. Check those details in the generated result because the model is not a deterministic layer editor.

Use a clear original image and inspect the output at full size. PNG is often a convenient input for crisp UI graphics. If your publishing system requires a specific pixel size or format, verify the downloaded file rather than assuming it matches the upload.

A small button has limited space. A replacement that is much longer than the original can crowd nearby icons, change line breaks or look unusually small. Use concise wording that represents the actual product and inspect the edges of the control.

If the whole interface needs a redesign, the source application or design tool is the right place to make the change. This editor redraws existing wording on the screenshot; it does not produce an interactive interface or update the application itself.

Translation mode can help prepare a language version of an image, but translated text should be reviewed by a fluent speaker and checked against the live localized product. Product names, date formats and UI labels may require approved terminology.

App stores publish device-specific screenshot requirements. Consult the relevant store's current specification and compare the output dimensions before upload. If the real application is available in that locale, capturing the real localized UI is a reliable way to confirm the screen accurately represents the product.

Suppose an application changes the text on a button after an onboarding screenshot was exported. Use a screenshot you own, enter the complete old button label and the new approved wording, then compare the edited result with the actual product. The example on this page shows a test edit from Start free trial to Get started.

Check the button's outline, spacing and position after the edit. A generated result may change surrounding details even when the request focuses on one label. If the application is available in the correct state, a fresh capture provides the most direct evidence of the real interface.

When a feature is renamed, a help article may need more than a changed image. Update the written instructions and the screenshot together, and verify the sequence in the live product. If a button moved or the workflow changed, changing only the label in a static screenshot can mislead the reader.

Use separate text pairs for different labels on the same screenshot. The editor accepts up to five pairs on one image. For multiple screenshots, submit each image separately and review the set for consistent wording, dimensions and visual presentation.

An edited screenshot can be useful during a design review when the goal is to compare possible wording. Clearly identify a proposed screen as a mockup when it does not represent a live feature. Keep a copy of the source so colleagues can understand the change and review it in context.

Do not edit communications or transaction evidence to falsify what happened. The acceptable-use policy excludes deceptive alterations of chats, payments and account records. The editor is for authorized product images and honest design work.

A screenshot used on an app store should show the real product and meet the store's current image specifications. Check the output dimensions, device frame, text and product state. The editor requests the original framing, but a generated file can differ in exact pixel size.

For a localized screenshot, confirm the language is supported by the product and ask a fluent speaker to review the wording. Apple's current screenshot specifications are linked in the further-reading section; other destinations may have different requirements.