Clean
A light, high-contrast card with a simple platform label, a short generated title, and your prompt text in a legible sans-serif layout.
We took the real AI PromptShot generator — the same editor, templates, and PNG export pipeline every visitor uses — and ran it through a controlled test: all 8 templates, all 4 export sizes, and 3 deterministic test prompts, then recorded exactly what the product actually did. No invented measurements, no simulated renderer. This page reports what we found, including the parts that turned out less dramatic than we expected.
Create a PromptShotOn September 12, 2026, we automated the live generator at /#creator with Playwright — the same browser-automation suite that covers the rest of the product — and drove it through every combination of the 8 real templates (Clean, Social, Developer, Terminal, Editorial, Research, Notebook, Minimal) and all 4 real export sizes (Landscape 1200×675, Square 1080×1080, Wide 1600×900, Large Square 1200×1200) with 3 controlled test prompts, for 96 cases:
For each case, the test filled the real #prompt-input, clicked the real template card and size chip, read the product's own pre-export fit check (the same checkPromptFit function the Download/Copy/Share buttons call before rendering), then clicked Download PNG and saved the actual exported file. Every one of the 96 cases produced a valid, non-empty PNG at the exact target dimensions (0 export failures). This never touches a server — PromptShot's export is a client-side canvas render, so nothing here reads or writes production data.
These are synthetic prompts written specifically for this experiment, not real user submissions, and this is one controlled test run — not a user study. See Methodology and limitations for exactly what that does and doesn't cover.
The headline result: across all 96 cases, the real exported PNG was never truncated — 0 of 96 cases triggered the product's own truncation warning. Every template handled every one of the 3 test prompts cleanly at every export size. The table below shows the one thing that did vary: whether the prompt visually clipped in the live on-screen preview before export (a separate, more conservative check than what actually gets exported — see below). This outcome was identical across all 8 templates for a given prompt and size, so it collapses to one grid rather than 8 repeated ones.
| Test prompt | Landscape | Square | Wide | Large Square |
|---|---|---|---|---|
| Short / general prompt (130 chars) | Fits | Fits | Fits | Fits |
| Long / structured research prompt (822 chars) | Clips | Fits | Clips | Fits |
| Developer / code prompt (620 chars) | Clips | Clips | Clips | Clips |
"Clips" means the on-screen live preview visually cut off before you'd even export — the real downloaded PNG was not truncated in any of these 96 cases. Result is the same across all 8 templates for a given cell.
Because none of the 3 core prompts (up to 822 characters) truncated a real export anywhere, we ran a supplementary experiment with one deliberately much longer, clearly-labeled stress prompt to find where real export truncation actually begins:
| Stress prompt | Landscape | Square | Wide | Large Square |
|---|---|---|---|---|
| 3,366 characters | Clips | Fits | Fits | Fits |
Here "Clips" means the real exported PNG itself was shortened with an ellipsis (the product's own truncation warning fired) — not just the preview. Identical across all 8 templates at this size.
Every image below is an unedited PNG downloaded during this test run through the real export button — not a mockup or a recreation.








Within the lengths we tested (up to 822 characters), template choice did not change whether a prompt fit — every template exported every prompt cleanly at every size. What actually differs between templates in this experiment is visual style and default platform/theme pairing, not raw capacity:
The honest finding here is that, within realistic prompt lengths, we could not make the real export crowd or clip at all — that only appeared once we pushed a stress prompt to 3,366 characters, and even then only at one size (Landscape), identically across every template. What we did find crowding — in 48 of the 96 core cases — was the live on-screen preview, which uses a simpler rule (a fixed maximum number of visible lines — 12 for Landscape/Wide, 20 for Square/Large Square) rather than the real export's shrink-then-truncate logic. That means the editor can visually look like it's cutting your prompt off when the PNG you'd actually download is not. If the live preview looks crowded, our data says: try Download PNG before assuming the prompt needs to be shortened — in every case we tested, the real export handled more than the preview appeared to.
Because line-fit in this experiment was governed by export size and prompt shape rather than by template, the technical outcome (rendered, exported, not truncated) was identical across all 8 templates for every prompt we tested. What differs is the visual treatment and the default platform/size pairing, summarized below from each template's own definition:
A light, high-contrast card with a simple platform label, a short generated title, and your prompt text in a legible sans-serif layout.
A square card with a deep purple-to-navy gradient background, bright text, and generous padding so it reads well as a thumbnail.
A dark, near-black card with a monospace typeface and a subtle border — styled like a code editor rather than a social graphic.
A wide, dark canvas with monospace type throughout, echoing a terminal window more than a typical prompt card.
A warm paper-toned background with serif-adjacent spacing and a large square canvas built for reading, not just scanning.
A light, landscape card with plenty of whitespace and a clear hierarchy between the topic and the prompt body.
A square, paper-toned canvas with a soft, informal feel — closer to a notebook page than a polished slide.
A square, neutral card with restrained color and spacing — the plainest of the eight PromptShot styles.
This is a controlled product test, not a user study, and not a statistically representative sample of every prompt PromptShot will ever see. Specifically:
The automated test itself lives in the codebase (a Playwright fixture that drives the real generator and records real results) and can be re-run to reproduce or update these numbers.