A translated label can make an image less accurate. It might turn an English-only interface into an apparent Swedish product, move a date into the wrong calendar cell or obscure the control the image was meant to explain. Localising ChatGPT ad imagery requires a visual accuracy check as well as a text replacement.
This workflow covers the image itself: source versions, embedded interface text, dates, product details and annotations. For decisions about natural headline phrasing and the meaning of the offer, use the separate Swedish-to-English copy adaptation guide. The task here is to produce an image whose visible details are correct in each version.
Start with a verified interface capture
Consider a fictional scheduling service for small workshops. The ad image shows a shared job calendar and the control used to view a technician’s assigned work. The English interface is available, while a Swedish marketing page also exists. That combination does not establish that Swedish menus are available inside the product.
Check the product’s actual language options before asking a designer to change any controls in the image. If a supported Swedish interface exists, capture that version using the same illustrative calendar state. If it does not, retain an accurate English view or choose a clearly illustrative diagram that explains the workflow without impersonating a product screen.
Do not silently paint Swedish labels onto an English screenshot. The result would demonstrate a product version that the source does not establish. Cropping out an irrelevant label can be reasonable, but hiding the interface language is not useful when that language is important to the buyer’s understanding of the service.
Separate embedded content from editorial annotations
Create a short inventory of visible text. In the workshop example, menu labels and calendar headings belong to the interface. A designer’s arrow saying assigned jobs is an editorial annotation. Fictional technician names and appointment titles are sample data. Each category has a different revision method.
| Element | Appropriate source for a change | What to inspect |
|---|---|---|
| Interface control | Genuine supported product version | The control exists and performs the shown action |
| Calendar date | Correctly configured source view | Date, weekday and month agree |
| Sample appointment | Deliberately prepared fictional data | The label remains illustrative rather than customer evidence |
| Explanatory callout | Approved translation in an editable layer | The arrow still identifies the same control |
Retain the distinction between sample data and genuine evidence. Translating a fictional appointment should not introduce a named customer or a measured completion result. If the working file lacks enough detail to establish what is sample data, resolve that question before preparing the language variants.
Review dates as a complete visual system
A date such as 04/05 can be ambiguous. The surrounding month heading and weekday may help a reader interpret it, but the image should not rely on conflicting signals. Inspect the calendar title, individual cells and any appointment tooltip together.
Where the application offers a relevant date setting, capture the intended format from the actual product. Avoid replacing one date by hand while leaving neighbouring dates in a different notation. If a schematic illustration is used instead, label it accordingly and make its date convention consistent throughout.
The same reasoning applies to times and durations. Do not convert one appointment into a different time representation without checking its start, end and visible duration. A translated callout must still point to the event it describes. These are checks of the illustration’s internal consistency, not claims about how the advertising platform handles time zones.
Verify physical variants and packaging when pictured
Not every localised image is a software screen. If a creative shows a physical product, compare the pictured variant against the one offered at its intended destination. Different connectors, fittings or included accessories may require a different source image. A matching product name alone is not enough.
Treat text printed on packaging as part of the pictured object. Use an appropriate original if the package differs by market. Replacing the printed language with a graphic edit can create packaging that is never supplied. If the package adds no useful explanation, choose a composition that shows the relevant product feature without it.
Measurements need both numerical and visual verification. An adapted unit should describe the same physical dimension, and its line should terminate at the same points. The overall width of a product is not interchangeable with a usable internal clearance. Changing a number correctly cannot fix a line that now measures the wrong space.
Reposition annotations without changing their referent
Return to the scheduling image. A translated callout may be longer than assigned jobs. Give the label more room, change its line break or move its box before reducing the type size. Then check that the leader line still points to the relevant control rather than an adjacent calendar event.
Inspect what the label covers. A callout that hides a selected technician’s name can make the view seem to show everyone’s work. An arrow covering a filter indicator can remove the explanation of why only some jobs appear. Localisation has changed the meaning even though the words are correct.
Review the crop after moving annotations. A label near the edge may lose a word or its connection to the interface in a tighter composition. Compare the actual exported images at the same review size. Make corrections in the editable source so the next revision retains the relationship between labels, arrows and the underlying capture.
Four visible details to check
- Actual interface
Capture a supported interface language. Do not paint Swedish controls onto an English-only product.
- Date system
Check date, weekday and month together. Replacing one calendar cell can leave conflicting formats.
- Callout placement
Move the translated label while keeping its arrow on the assigned-jobs control and filters visible.
- Final export
Inspect the actual crop: the label, connecting arrow and relevant calendar control must remain understandable.
Hand over evidence of the visual changes
Keep the verified source capture, product version, sample-data note and exported language variants together. Record meaningful differences: supported interface changed, date format adjusted, callout moved, original package replaced. The source asset preparation guide explains how to keep these records connected to the files.
OpenAI’s standard ad combines imagery with title, body and destination. Campaign Management. Inspect the final combination while keeping the image review focused on visible accuracy. Context hints supply context rather than exact keywords or guaranteed delivery. Targeting.
Approve the exact exports after checking interface authenticity, date consistency and annotation placement. A translated design file is only an intermediate asset. The completed image should show a version that exists and preserve the visual relationships that explain the product’s capability.
Sources and scope
Decide which visible image elements require localisation and verify genuine interface versions, date representations, product details and annotation geometry in each export.
Working methods and examples are editorial suggestions. Check current platform requirements and available features before implementation.