Recraft 4.1 for app screenshots
Recraft 4.1 letters UI chrome — buttons, tab labels, empty states. Do not ask a video model to typeset a settings screen.
App Store and Play screenshots fail when the chrome is mush. The phone frame can be pretty. If “Start trial,” “Inbox,” and the empty-state line cannot be read at phone size, the listing is a mood board. Recraft 4.1 Text to Image is the 3-credit stills row with strong style control and consistency — the right generate when the picture is a UI, not a cinematic of someone holding a phone.
This is not a general Recraft lock-then-animate guide. Motion is usually the wrong next step for a screenshot set. The store wants a row of stills. Letter them. Proof them. Stop.
Screenshots are lettering, not a product film
A store screenshot is a poster of an interface. Buttons, tab bars, settings rows, a price, a three-word empty state. Those strings are the product. A video model will treat them as texture and crawl them while a fake thumb scrolls. You will not know whether you have a copy bug or a motion bug. You will also have seconds you cannot paste into App Store Connect.
Recraft 4.1 is image content type, text-to-image, 3 credits, no durations, no audio. Aspects on the record include 1:1, 16:9, 9:16, 4:3, 3:4. Pick the ratio the store slot actually uses on this row. A 1:1 UI you later crop into a 9:16 iPhone slot is a crop of a layout, not a screenshot. Apple and Google slots are tall. Set 9:16 if that is the slot. Do not leave it square “for now.”
requires_image is false. This is a generate of a screen, not an edit of a capture — unless you already have a capture, in which case an edit-image row is the honest delta. Re-rolling 4.1 and calling it the same screenshot is a new identity with similar vibes.
Style control and consistency are why Recraft belongs on UI. A five-screenshot set has to look like one app: same chrome weight, same corner radius language, same type scale. Photoreal workhorses will give you five different glass phones with five cousin typefaces. Recraft’s listed job is the pack look. Use it as a pack look.
The door is text to image. Recraft V4 is the previous generation on the same roster, 4 credits, more design punch. Use 4.1 when you already know the Recraft look and you are iterating chrome. Use V4 when the first frame of the set still needs a designer-shaped lockup. Do not name-swap them in a brief.
Quote the chrome
Unquoted UI copy gets paraphrased. “A fitness app home screen with a friendly CTA” will letter something that is almost a button. Quote the strings you would ship:
- The tab labels:
Home,Log,Pay,You. - The primary button:
Start 7-day trial. - The empty state:
No workouts yet. - The settings row:
Notifications.
Cap the count. A screenshot can carry a headline, a primary control, and a short helper. It cannot carry a settings dump. Past about a dozen words on the glass, generate the layout with space for type and composite the real UI font later. Recraft will letter short display text. It will not be your localisation file.
Write the chrome like a design brief, not a cinematic prompt:
- Device: iPhone slot or Android slot, not “a hand holding a futuristic slab” unless the hand is the brief.
- Hierarchy: one primary control, secondary rows quieter.
- What is not text: the chart is a chart, the avatar is an avatar, the wood grain is not a wordmark.
- Dark mode or light mode, named. “Premium” is not a mode.
Proof at 100 percent. Read every control aloud. A wrong character on a CTA is a different SKU. A swapped tab label is a different IA. Near-correct (Start 7 day trail) is a fail. Regenerating the whole set to fix one button is how the other four screens drift. Fix one screen, then match.
Do not ask Recraft to invent a real OS status bar down to carrier and time unless those strings are the joke. Fake 5:00 and 100% battery are fine as dressing. Fake your button copy is not.
Style control is why Recraft
Other lettering stills exist. Ideogram V4 is 5 credits, posters and logos, accurate text rendering — the right row when the screenshot is really a marketing poster with a huge wordmark and a phone as a prop. Seedream 5.0 Pro is 6 credits, 14-language dense layouts — the right row when the screen is a dashboard with a table. GPT Image 2 is 9 credits (was 17), 4K, strong prompt adherence — useful when the UI sits inside a reasoned scene (a named desk, a named device). Recraft 4.1 is the middle of that shelf for interface as the picture: consistent chrome across a set, style locked, 3 credits a frame.
That 3-credit sticker is why teams skip proofreading. “It’s only a still.” The store listing is a still. The still is the listing. Animating a miss does not help App Review.
Consistency across the set:
- Same prompt suffix for chrome: corner radius, type weight, background colour, status-bar treatment.
- Same aspect for every slot in the row.
- Same device language. Mixing a notchless slab with a Dynamic Island look in one listing is a different app.
- Kill the frame that broke the type. Do not average it.
If member three already looks like a different product, members one and two will not save the listing. Re-roll three. Three credits.
Localisation is a new generate per language, not a video retake. Quote the German strings. Proof the German strings. Do not I2V the English screen and hope Omni Flash typesets Kostenlos testen.
Overlay vs generate for store copy
Two kinds of words sit on a screenshot.
In the glass. Tab labels, button titles, empty states, in-app prices that are part of the UI. Generate those on Recraft (or composite a real capture). They have to survive a zoom into the phone.
Beside the glass. The marketing headline in the screenshot slot — “Track workouts without a spreadsheet,” the App Store caption above the device. That line is often overlay, because you will change it in A/B tests and because licensed brand fonts rarely belong inside a generate. Text overlay is copy you wrote. It is not Recraft.
Mixing them is how a CTA exists twice, once misspelled in the pixels and once correctly in the caption. Pick: either the button is the claim, or the overlay is the claim. Not both fighting.
Do not generate the whole listing as a 6-second video and pull frames. You will review motion for a look you never locked, and the store will still want stills. Recraft 4.1 exists so the look is a stills conversation at 3 credits.
If a real capture exists and only one label is wrong, that is an edit-image job, not a new 4.1 scene. Point at the control. Keep the rest of the screen.
Article 50 is rarely the screenshot problem — UI comps are not usually deepfakes — but a generated person in the screen (a fake testimonial face) is a different object. Do not invent a customer. Use a silhouette, an avatar you own, or no face.
When the chrome reads, you have a screenshot. Sign up and generate the set as stills, not as a product film.
FAQ
Is Recraft 4.1 a video model I can scroll for a preview GIF?
No. Image content type, no durations. If you need a short preview of the UI in motion, lock the stills first, then image-to-video on a keeper — knowing type may drift. Most store listings should stay stills.
Why not Ideogram for the same buttons?
Ideogram V4 is the poster-and-logo specialist at 5 credits. Use it when the screenshot is a wordmark-led marketing frame. Use Recraft 4.1 when the set has to look like one app’s chrome. Quote the strings either way. Proof either way.
Can I generate tiny settings copy and ship it?
Not as the source of truth. Short display text on a primary control will often hold. A full settings dump will not. Composite real UI type for dense tables, legal, and anything you will restyle next week.