How to Create Dummy Data for Screenshots: Names, Numbers, and Photos
Most of what shows up in a screenshot is data: the names in a list, balances and scores, profile photos, chat bubbles. If the values you used during development — 'test01', 'asdf', 'John Doe' — are still there, the screen looks like an unfinished product no matter how good the layout is. Go the other way and shoot a real account with your friends' names in it, and you have a privacy problem.
This guide covers how to build dummy data that looks plausible but belongs to no one. It goes through names, numbers, and photos in that order, with principles and examples for each, and ends with a pre-shoot checklist.
Dummy Data Is Part of the Message
Users look at the data in a screenshot and guess who the app is for. In a hypothetical recipe app, a list that reads 'Recipe 1, Recipe 2' says something different from one that reads 'Tomato and egg stir-fry, 10-minute braised tofu'. The first screen shows a feature; the second shows a use case — quick meals after work.
So treat dummy data as material you choose to fit the message of the set, not as values you fill in at the last minute. In that same recipe app, if the target is people living alone, the screen should show single-serving dishes and ways to use up leftovers; if it's families with kids, lunchboxes and snacks. For apps where a text list fills most of the screen, like a to-do app, there are more examples in Screenshots for Productivity and To-Do Apps.
No Real People, No Real Personal Data
This is the first rule. Screenshots spread to the store, to ads, and to social media, and once they're out they're hard to recall. Replace all of the following with fictional values before you shoot, even if they only live in a test account.
- Real names and actual usernames of friends, family, or teammates, and real friend lists
- Anything that could point to a specific person: phone numbers, email addresses, street addresses, account or card numbers
- Celebrity and public-figure names, real company names and trademarks, real business names
- Actual user posts, reviews, or chat messages pulled from the production server
For email addresses, use the example.com family of domains, which is reserved for exactly this purpose, so you never collide with a real address. Phone numbers are riskier: a number you make up at random may belong to someone, so mask the middle digits with asterisks or pick a screen where no number appears at all. If you're shooting from a development build, set up a dedicated screenshot account. That keeps a real name from sneaking into a friend list or a notification. Tidy up the status bar and notifications before you shoot, too.
Names: Varied, and Not All the Same Length
Fake names look fake mostly because they're too typical or too similar to each other. Names straight out of a textbook example, or a list where the same surname and the same number of letters keep repeating, give the game away immediately.
| Awkward | Natural | Why |
|---|---|---|
| User1, User2, User3 | acorn_jelly, sunny_kim, StarlightWalk | Usernames on a real service don't follow one format |
| John Smith, Jane Doe, Bob Jones | Priya Raman, Theo Lindqvist, Ana Sofía Castellanos | Skip the stock example names and mix up surnames and lengths |
| Every name the same length | One long name among short ones | It also proves the layout holds up when a long value comes in |
| Names from your home locale on every listing | Names that fit the locale | If you're making per-language sets, the names should match that culture too |
A name you invent could happen to match a famous person, so run a quick search on each one. If you're building per-language sets, localization covers more than captions — the names and date formats on screen need to change too. How Screenshot Localization Affects Downloads goes into that side of it.
Numbers: Not Round, and Consistent With Each Other
Numbers give themselves away even faster than names. A column of values like $10, 100 points, and 10,000 gold looks hand-typed. But a maxed-out value like 999,999, or anything unrealistically large, reads as exaggeration.
- Roughen the last digits. Use values that could actually occur: $12.80 instead of $12.00, 4,762 steps instead of 4,500.
- Avoid perfection. A screen where every goal is met, every review is five stars, and every progress bar is full is less believable, not more. A bar that isn't quite full says 'in use'.
- Keep the screens consistent. If the character is level 12 in the second screenshot and level 5 in the third, or the balance is different on every screen, attentive users will notice.
- Match the time. A status bar clock reading 9 AM next to a 'tonight's workout done' entry looks off. Match dates to the calendar, down to the day of the week, and for any value that reveals a specific year, ask whether it will still look fine after a long time on display.
- Format for the locale. Thousands separators, currency symbol position, and date order all vary by language and region.
Photos and Images: Check the Rights First
Profile photos, product shots, and post thumbnails bring a screen to life, and they're also where rights problems come up most often. What to check depends on where the image came from.
| Source | What to Check |
|---|---|
| Photos you took yourself | Whether anyone whose face is visible has consented, and whether someone else's logo or artwork is prominent in the background |
| Stock images | Whether the license allows commercial use such as app promotion, and for photos of people, whether a model release covers them |
| Generated images | Whether the tool's terms allow commercial use, and whether the result resembles a real person or a well-known character |
| Content from friends or testers | Best avoided even with permission, since you'd have to replace it if they later ask you to take it down |
| Films, music, other games | Posters, album covers, and third-party characters don't go in, even as placeholders |
If usable photos are hard to come by, illustrated avatars or initial icons work just fine. Keep a note of which image came from where. It makes rechecking much easier when you later reuse the screenshots in ads.
Keep the Dummy Data as One Set
You'll use the same dummy data again at the next update. Collect every value that appears on screen in a single table, and you can recreate the same state quickly when you reshoot. For a hypothetical farm management game, it might look like this.
| Screen | Item | Value | Note |
|---|---|---|---|
| Farm overview | Gold on hand, level | 3,480 gold, level 14 | Stay at level 14 in every screenshot |
| Shop | Gold after purchase | 2,930 gold | Reduced by exactly the seed price |
| Leaderboard | Other players' usernames | StarlightWalk, sunny_kim, PotatoKingdom | No real user names; my rank somewhere in the middle |
For an app, turn this table into a seed data file; for a game, into a save file. Then you can repeat the shoot for each language by changing only the values. Drop the resulting screens into a StoreShot template and you can manage per-language captions in locale tabs, which makes it easy to keep the on-screen data and the caption in the same language.
Pre-Shoot Checklist
- No real names, real usernames, or real contact details anywhere on screen
- No development strings like 'test', 'asdf', or 'lorem ipsum' left behind
- Numbers that aren't too round or too perfect
- Levels, balances, and dates consistent from one screenshot to the next
- Number and date formats that match the target locale
- A source and usage scope you can explain for every photo
- No third-party trademarks, logos, or characters, even in the background
Exposed development strings or unfinished copy can also cause trouble in review. The cases that come up most often are collected in Why Your App Gets Rejected Over Screenshots (And How to Avoid It).
Wrapping Up
Good dummy data doesn't draw attention to itself. If the viewer simply accepts the screen as 'an app someone actually uses', it has done its job. Names that belong to no one, numbers that could really occur, images whose source you can explain — stick to those three and the effort you put into the layout won't be undercut by the data.