A practical message design guide
Create an iMessage mockup that feels intentional.
A convincing text-message mockup is less about copying every pixel and more about making the conversation, spacing, and device details agree with one another.
Plan the conversation first
Decide what the screenshot needs to communicate before changing the visual settings. A useful mockup usually has one job: reveal a decision, show a reaction, explain a product flow, or establish a moment in a story.
Write the exchange in plain text first. Keep each bubble focused on one thought and vary message length so the result does not look mechanically generated. For a storyboard, the final bubble should make the next action clear. For a product demo, the important feature or confirmation should be visible without requiring the audience to read a long transcript.
| Use case | Conversation goal | Recommended length |
|---|---|---|
| Story or video | Establish a reveal or decision | 3–6 bubbles |
| Product demo | Show a trigger and confirmation | 2–4 bubbles |
| Presentation | Support one talking point | 2–5 bubbles |
| Thumbnail | Communicate one strong moment | 1–3 bubbles |
Build the screen step by step
- Upload an optional fictional avatar or use the generated initial.
- Enter the recipient name shown at the top of the iMessage screen.
- Add or rewrite each message, then set it as sent or received.
- Reorder messages until the exchange has a clear beginning and ending.
- Set the device time and choose a 12-hour or 24-hour format.
- Compare light and dark appearances against the final background.
- Review the complete preview before downloading the PNG.
The editor above this guide is the source of truth. If a label, bubble, or status detail looks crowded in the live preview, shorten it before export instead of trying to repair it later in an image editor.
Choose message direction
Sent messages represent the device owner. Received messages belong to the contact shown at the top of the screen. Check the direction after every edit, especially when you rewrite both sides of a conversation.
- Use sent for the person holding the phone.
- Use received for the contact or service replying.
- Alternate only when the conversation naturally calls for it.
- Keep consecutive messages on the same side when one person naturally sends several short thoughts.
Write a believable example
A believable exchange includes a clear relationship and a reason for the conversation. Avoid filling every bubble with exposition.
Scenario: a designer is sending an updated presentation before a meeting.
- Received: “Can you send the version with the new pricing slide?”
- Sent: “Yes, I’m exporting it now.”
- Sent: “I’ll send the PDF in five minutes.”
- Received: “Perfect. I’ll open with that version.”
This works because the messages have different lengths, the direction is obvious, and the final reply closes the scene. Replace the example with your own fictional details rather than copying a real private conversation.
Match the device details
The time, contact name, status icons, and conversation copy should support the same moment. If the conversation says “good morning,” a late-night device time will feel wrong even when the visual styling is accurate.
Use the 24-hour option when the audience or setting expects it. Keep the contact label short enough to fit the header, and avoid adding more detail than the screenshot needs.
Before exporting, verify these details together:
- the device time matches the scene;
- the recipient name fits on one line;
- sent and received colors are easy to distinguish;
- punctuation and capitalization feel consistent;
- the last bubble is fully visible in the frame.
Export and place the image
Review the full preview before downloading. Look for clipped bubbles, accidental line breaks, inconsistent punctuation, and empty messages. The exported PNG is designed for presentations, storyboards, thumbnails, and social content.
The generator exports at a higher pixel ratio than the on-screen preview. Download the high-resolution version and scale it down in your video or design editor. Avoid converting transparent assets to JPEG and avoid enlarging a small copy after export.
Place the phone on a background with enough contrast around the device edge. Leave safe space around the screen when the final image will be cropped for a social platform.
Troubleshoot common problems
The contact name wraps or feels crowded
Shorten the label, remove unnecessary emoji, or use a first name instead of a long account description.
A message bubble becomes too narrow
Break the copy into two natural messages or replace a long URL with a fictional short link. Do not insert manual spaces to force wrapping.
The exported image does not match the intended scene
Return to the live preview and check appearance, time format, direction, and message order together. Most inconsistencies come from one setting being edited independently from the conversation.
Common questions
Does the generator add a watermark?
No. The current message generator exports a clean PNG without a watermark.
Can I use the image in commercial work?
You can use the mockup in design, education, storytelling, and presentation work. Do not use generated conversations to impersonate a real person, fabricate evidence, or mislead an audience.
Is this an official Apple or iMessage tool?
No. Fake Generator is an independent mockup tool and is not affiliated with or endorsed by Apple. Use the result as an illustrative screen, not as proof of an authentic conversation.