How to Use Fake Chat Screenshots for App Store Previews
A store listing has about five seconds to explain an app. For a chat app, a messaging feature, or any product where the conversation is the product, a fake chat screenshot can do that job faster than a paragraph: one short exchange shows the tone, the pace and the kind of thing people say in it.
The catch is that a store preview is not a meme. Apple and Google both expect screenshots to show the app in use, and a chat mockup that looks like a real person's private conversation will read as deceptive — and can be rejected. This guide builds the preview the honest way: a short fictional exchange, exported from ChatShot, placed on a store-size canvas with a headline, and checked against the store's current rules before it is submitted.
The short version
Step 1: Pick one conversation, not your whole app
A preview frame holds one idea. Choose the single exchange that makes a browser understand the app: a first message arriving, a plan coming together, a support question answered in two lines. If your app does several kinds of chat, make one frame per kind — do not cram three use cases into one screenshot.
Write the exchange before you open the generator: two voices, one idea per message, 6–10 messages. Keep names fictional and short ("Maya", "Leo"), and keep the topic obviously illustrative — a weekend plan, a class reminder, a delivery update — never a real person's words.
Step 2: Build the chat in the matching generator
Open the generator for the platform your screenshot should look like: the WhatsApp chat generator, the Telegram chat generator or the iMessage generator. Describe the scenario, read the generated draft as a stranger would, and rewrite any line that sounds scripted. Click a bubble to edit its text; use "+" to insert a message on your side; delete with ×.
Check the header before you export: the contact name, the status line, the timestamps and the read ticks come with the generated conversation, and the editor does not let you set them message by message. If a timestamp contradicts your story, regenerate or rewrite the wording. Avatars are the contact's initials — there is no photo upload — and exports render the classic light theme. Both are fine for a preview: a clean light chat reads well at store size.
Step 3: Export the chat image
Export the finished chat as an image from the generator. This is the raw material, not the finished preview: the export is the chat itself, at the generator's own size, with no headline and no store framing. Do not upload it to a store as-is — the next step is where it becomes a preview.

A real export from ChatShot's WhatsApp generator: Maya and Leo planning a Saturday hike, 8 short messages, fictional names.
Step 4: Place it on a store-size canvas
Open a design tool and make a canvas at the size the store wants, then place the exported chat on it with a headline and a plain background. The sizes below were checked against 2026 sizing guides in November 2026; Apple and Google change these pages, so confirm them in App Store Connect and the Play Console before you submit.
- App Store, iPhone: use the 6.9-inch set — 1320×2868, 1290×2796 or 1260×2736 px portrait. Apple accepts 1–10 screenshots per device size, JPEG or PNG with no alpha. Upload this set and Apple scales it for smaller iPhones.
- Google Play, phone: 1080×1920 px portrait (9:16) is the recommended size. Play accepts JPEG or 24-bit PNG with no alpha, each side between 320 and 3840 px, with the long side at most twice the short side. You need at least 2 screenshots to publish, up to 8 per device type.
Leave breathing room: the chat should fill most of the frame, with the headline in one short line and no more than one supporting line. A frame that is half headline and half chat explains neither.
Step 5: Write one headline per frame
Each preview frame gets one benefit, in the user's words: "Plan the weekend in one thread", "Support answers in two messages", "Your class group, without the noise". The headline sits above or below the chat, never across it, and it must be true of the app — a chat mockup that promises a feature the app does not have is a rejection waiting to happen.
If you are localising the listing, translate the headline and the chat together. A screenshot in English on a Japanese listing tells the browser the preview was not made for them.
Step 6: Check it as a stranger, then submit
Before uploading, look at the finished frame and ask three questions:
Only when all three pass should the frame go into the listing. Keep the exported chat image and the canvas file together, so a later store-size change is a re-export, not a rebuild.
Frequently asked questions
Can I upload the ChatShot export directly to the App Store? No — not as a preview. The export is the chat image at the generator's own size. Place it on a 1320×2868 px (or 1290×2796 / 1260×2736) canvas with a headline first; Apple requires exact dimensions for the 6.9-inch set.
What size should Google Play screenshots be? 1080×1920 px portrait is the recommended phone size, JPEG or 24-bit PNG with no alpha, each side between 320 and 3840 px, long side at most twice the short side. At least 2 screenshots to publish, up to 8 per device type.
Can the chat show a real conversation from my app? Do not use a real person's messages, name or photo in a store preview. Build the exchange from fictional names and an everyday scenario, and label the mockup as illustrative wherever the store allows it.
Which platform should the chat look like? Whichever your app actually is. A WhatsApp-style frame for a Telegram app, or an iMessage frame for an Android-only app, will confuse the exact people the preview is meant to convince. Match the skin to the product.
Does ChatShot export in dark mode? No. Exports render the classic light theme; a dark renderer is on the roadmap. The light export is the right choice for a store preview in any case — it stays legible at small sizes.