Pick the shortest route from raw product screens to the exact asset you need.
01
The quick answer
Screenhance has specialized workspaces because a social card, a store listing and a product demo need different controls. Start with the destination of the finished asset, not the type of screenshot you currently have.
| What you need | Best place to start |
|---|---|
| A mockup, website graphic, social card or Product Hunt image | Visual Editor |
| A coordinated iOS, Google Play or Chrome Web Store screenshot set | Store screenshot editor |
| A recorded or animated product demo | Studio |
| Several launch assets from one product brief | Launch Kit |
| A mockup made from layers already selected in Figma | Screenhance Mockups for Figma |
02
Use the destination as your decision guide
- Choose the Visual Editor when you need free-form composition, multiple artboards, frames, physical scenes, text, assets, backgrounds or motion.
- Choose the store editor when every slide belongs to one listing and must share a platform, device size, language set and export package.
- Choose Studio when time is part of the story: a screen recording, an animated sequence, cursor movement, captions, zooms or annotations.
- Choose Launch Kit when you want Screenhance to propose a family of launch assets first and you plan to refine individual outputs afterwards.
03
Prepare the right source material
- 1Capture clean product screens at the largest practical size. Hide private data, browser extensions and temporary debug UI first.
- 2Collect your logo, brand colors and the short product claims you want the audience to remember.
- 3Decide the destination and aspect ratio before polishing details. A store screenshot and a website hero often need different crops of the same UI.
- 4Start from a template close to the final structure, then replace its sample media before adjusting type, colors and motion.