Every time you ship a feature, you take a screenshot. Most founders post that screenshot directly to Twitter/X or Instagram — same raw PNG, no frame, no context, no headline. It gets a few likes from people who already use the app and almost nobody else.
The screenshot isn't the problem. The workflow is. A single app screenshot contains the raw material for five distinct, platform-optimised marketing assets. Most founders use maybe one of them. This guide gives you the system for using all five — and producing them in a single 25-minute session.
The Raw Screenshot vs. The Finished Asset
There's a meaningful difference between a raw screenshot and a finished social media asset, and it's the difference between content that gets scrolled past and content that stops the scroll.
A raw screenshot is the PNG you exported from your simulator or device. Full-interface view, no brand context, no device frame, no headline. It looks like a developer's notes to themselves — useful for documentation, wrong for social media.
A finished asset is that same screenshot + a device frame + a brand-consistent background + a benefit headline + your logo. It looks like a product, not a debug capture. It signals that someone made this intentionally, which signals that the product behind it was made intentionally too.
The gap between raw and finished is what most screenshot-to-social-media guides miss. They focus on which tool to use or how to add drop shadows. The real insight is that the raw screenshot is source material — the asset is what you build from it.
What One App Screenshot Becomes: The 5-Asset System
One source screenshot can produce five platform-native assets. Here's the full system:
| Asset | Platform | Dimensions | What to Crop To | Caption Convention |
|---|---|---|---|---|
| Twitter/X post | Twitter/X | 1200×675 px | Key feature UI with ~25% surrounding context | 5–10 words, punchy benefit: "Now you can sort by priority" |
| Instagram feed post | 1080×1080 px | Tight square crop on the feature element | 1–2 sentence benefit + hashtags | |
| OG image | All (link preview) | 1200×630 px | Feature UI + product name visible | Release note title: "v2.4 — Priority sorting" |
| Meta ad creative | Meta/Instagram | 1080×1350 px | Centered UI, headline above or below | Outcome-first: "Spend 30% less time on task management" |
| App Store screenshot | App Store / Google Play | 1320×2868 px (iPhone) / 1080×1920 px (Android) | Full-screen vertical, feature UI in top 60% | Short caption: "Sort by what matters" |
This is the full repurpose set for a major feature launch. You don't need all five every time — the decision framework is below — but for a meaningful new feature, all five are worth producing.
What to Crop to for Each Platform
The same screenshot at different aspect ratios shows different amounts of UI. Without intentional cropping, you get a full-interface view crammed into a square, a vertical format showing two pixels of your app, or a landscape crop that cuts off the key feature entirely.
The rule: crop to the specific UI element that's new, not the full interface. If you shipped a new dashboard card, crop to the card. If you shipped a new settings panel, crop to the panel.
Twitter/X (1200×675 — landscape): Wide format works well for showing a feature in context. Crop to include 20–30% surrounding UI as context, keeping the new feature clearly centered. Enough context to understand the feature, not so much that the key element gets lost.
Instagram (1080×1080 — square): The square crop forces a tighter focus. Crop directly to the feature element with minimal surrounding UI. If the feature requires context (a list with a new sort control), show just the top portion and the control — not the full screen.
OG image (1200×630 — wide landscape): The OG is a link preview thumbnail, often seen at 300–400px wide in a social feed. Test your draft at 25% zoom — if the key UI element isn't readable at that size, you're showing too much.
Meta ad (1080×1350 — portrait 4:5): Feature UI in the upper 60–70%, benefit headline in the lower 30–40%. The headline carries more weight in the ad format — make it specific: "Spend 30% less time on task management" beats "New sorting feature."
App Store screenshot (1320×2868 / 1080×1920 — tall vertical): Feature UI occupies the top 50–65% of the frame. Unlike other assets, App Store screenshots often skip the device frame — they're displayed in a gallery where a frame adds visual noise. See our App Store screenshot guide for full dimension specs and conversion rules.
The Caption Layer: What to Write for Each Platform
Most screenshot-to-social-media guides stop at sizing. They never address what to write — and the caption is often what converts a view into a click or a download.
Twitter/X: Short and specific. 5–10 words. State the outcome or the action. "Now you can sort tasks by priority." "Search just got 3x faster." "Dark mode. Finally." Brevity is a feature here — Twitter users are moving fast.
Instagram: Slightly longer benefit statement followed by a call to action. 1–2 sentences of context, then the CTA ("Try it now — link in bio"). Relevant hashtags at the end (3–5, not 30): #productupdate #appdesign #indieapp.
LinkedIn: Outcome-focused with professional framing. Lead with a quantifiable result if you have one ("Teams using [app] now spend 30% less time on task management") or a specific use case. Professional tone, no emoji unless your brand voice uses them.
OG image / Changelog: The caption is the changelog title and description. Convention: release version or release name as headline ("v2.4 — Priority Sorting"), then 1–3 bullets describing what changed. Documentation that doubles as link preview content.
App Store screenshot caption: Short, typically placed at top or bottom. 4–6 words, benefit-first. "Sort by what matters." "Your fastest route home." Must work at thumbnail size in the App Store gallery.
Full Repurpose vs. Minimal Repurpose: When to Do Which
Not every screenshot needs all five assets. Matching repurposing effort to shipping significance prevents both over-production and under-production.
Full 5-asset repurpose: New user-facing feature that meaningfully changes how someone uses the app. Something worth announcing. Generate all five and publish across relevant platforms within 24–48 hours of launch.
Minimal 2-asset repurpose: Bug fixes, performance improvements, small UX tweaks. Worth acknowledging publicly (transparency builds trust) but not worth a full kit. Generate the Twitter/X post and the OG image for the changelog entry. Skip the rest.
No repurposing: Backend work, infrastructure changes, database migrations — anything that doesn't change the user-facing experience. Don't manufacture content for sprints where nothing changed from the user's perspective.
This maps directly to the sprint types in the indie app founder weekly workflow: Feature Sprint = full repurpose, Improvement Sprint = minimal, Deep Work Sprint = skip.
Generating All 5 in 25 Minutes
The goal is a single session — not five separate tool opens across five days.
Step 1 — Capture the source screenshot (2 minutes) Take a clean screenshot of the feature. Populated with realistic data, cropped to the relevant region. No empty states, no loading spinners. Save it as your source file.
Step 2 — Generate all 5 assets in Framiq (18–20 minutes) Open Framiq, upload the screenshot, confirm your URL for brand extraction. Generate each of the five formats. For each, adjust the crop, the headline copy (using the platform caption conventions above), and any background/frame styling. Framiq reads your live site at generation time to extract your current brand colors, fonts, and logo — every asset in the set is automatically on-brand without manually re-entering any configuration. Export all five.
Step 3 — Distribute (3–5 minutes)
- Schedule Twitter/X and Instagram posts
- Drop the OG image into your CMS for the changelog entry
- Queue the Meta ad creative for your monthly refresh upload
- Submit the App Store screenshot with your version update if applicable
Total: 25 minutes from source screenshot to all five assets ready to distribute. For full platform routing detail, see the B2C app marketing assets guide.
Frequently Asked Questions
How do I turn a screenshot into a social media post?
Add four elements: (1) a device frame, (2) a brand-consistent background color, (3) a benefit headline of 5–10 words, and (4) your logo. These transform a raw screenshot into a finished social media asset. Then size it for the specific platform: 1200×675 for Twitter/X, 1080×1080 for Instagram, 1200×630 for OG images.
What size should app screenshots be for social media?
Twitter/X: 1200×675px. Instagram feed: 1080×1080px (square) or 1080×1350px (portrait). OG image (link preview): 1200×630px. Meta/Facebook feed ad: 1080×1350px. Stories/Reels: 1080×1920px. App Store (iPhone): 1320×2868px. Google Play: 1080×1920px. Each platform renders content differently — unsized screenshots get auto-cropped in ways that cut off the important parts.
Do I need to make all 5 assets every time I ship?
No. Match repurposing effort to shipping significance. Full 5-asset set for major new features. Twitter/X post plus OG image only for bug fixes or small improvements. No assets for backend or infrastructure-only sprints where nothing changed from the user's perspective. Over-producing for minor updates dilutes the signal.
How do I make my product screenshot look professional?
Apply four elements consistently: (1) device frame — a phone or laptop frame signals a polished product, (2) brand background — your primary color or a complementary neutral, (3) benefit headline — 5–8 words, outcome-focused, (4) your logo — small and consistent in the same corner every time. These four, applied consistently, are what separate professional-looking product screenshots from raw developer exports.
What is the best tool for repurposing app screenshots?
For a single-session full repurpose set (all 5 formats from one source screenshot), look for a tool that handles multi-format export and extracts brand from your URL rather than requiring manual template configuration. Template-based tools require manual brand setup and produce drift when your brand evolves. URL-extraction tools like Framiq read your live site at generation time so every asset in the set is automatically on-brand.