Build a chat-style image for a meme, a tutorial, a comic panel or a UI mock-up. Write the conversation as a script — a line starting with > is from you, < is from them, and [10:24] at the end sets a time — and the bubbles lay themselves out, sized to their content, on a canvas as tall as the conversation needs. The styling is intentionally generic: it reads as a messaging app without being any particular one, because a mock-up needs to look like a chat, not like evidence. This is for fiction, jokes, teaching and design. It is not for impersonating a real person or fabricating proof of something that did not happen, and the exported PNG carries nothing that identifies it as made up.
| You type | You get |
|---|---|
| < hey are you coming | A message from them |
| > on my way [10:24] | Your message, timestamped 10:24 |
| hey | No marker — treated as theirs |
| > see [this] now | Brackets mid-line stay as text |
For fiction, jokes, tutorials, comics and UI mock-ups, yes. Using it to impersonate a real person or a company, or to fabricate proof of a conversation that did not happen, is not okay and in many places is illegal — fabricated messages presented as real have been treated as forgery and as fraud. Be clear with your audience that it is made up.
No, and that is worth knowing rather than assuming. The export is a plain PNG with no watermark or hidden marking, so nothing in the file tells the next person who sees it that it was generated. Labelling it is your job.
Deliberately. The themes read as a chat interface without copying anyone's logo, wordmark or exact interface — that is both a trademark matter and the line between a mock-up and a forgery. If you need a pixel-exact reproduction of a real product, you are past what this tool is for.
One message per line. Start a line with > for your own messages and < for theirs, and put a time in square brackets at the end if you want one: "> on my way [10:24]". A line with no marker is treated as theirs.
Yes — they are measured and drawn like any other character, so bubbles size correctly around them.
The canvas grows with it and the whole thing is exported, rather than being cropped at a fixed height. A very long export makes a very tall image, which is usually the right answer for a chat.
No. The text of a mock-up is usually a joke about somebody, and it stays in your browser.
Conversations are written as a script rather than assembled in a form: a line beginning with an angle bracket sets who is speaking and a trailing bracketed time sets the timestamp. Typing a conversation is faster than filling in a list of rows, and a conversation is the shape the thing already has in your head. The layout is computed rather than fixed. Each bubble wraps its text to a maximum fraction of the width, then shrinks to hug its longest line — which is what makes a one-word reply look like a one-word reply instead of a full-width bar — and the canvas height is derived from the stack of bubbles rather than set in advance, because a mock-up cropped at the bottom is the one output this must never produce, and a fixed-height canvas with a scrollbar cannot be exported at all. Everything is drawn straight onto the canvas rather than screenshotted from DOM, so the export is exactly the layout that was measured. The styling is deliberately generic: three neutral palettes that read as a chat app without being any particular one. There is no logo, no wordmark, no reproduction of a real product's interface, and that is a design decision rather than an oversight. A mock-up for a meme, a tutorial screenshot or a UI demo needs to look like a chat; it does not need to look like evidence. The page says so, and the exported image is a plain PNG with no hidden marking — which is worth stating plainly, because it means nothing about the file identifies it as fabricated to whoever sees it next. Everything runs in the page: the text of a mock-up is often a joke about someone, and it is nobody else's business.