# Screenshot Treatment
When the user supplies an app / web / code / dashboard screenshot, **do not** drop it raw into a `.frame-img`. The aspect ratio mismatch crops UI and the harsh edge looks SaaS-y. Use `.frame-shot` instead — a sibling class added to both seed templates.
## When to reach for it
- App / Web UI capture — anything with a status bar, tab bar, toolbar, or window chrome.
- Code / terminal screenshots.
- Dashboard / chart screenshots that need to keep every label readable.
- IDE captures where text density matters more than composition.
For **photographic** content (people, scenery, products) — keep using `.frame-img`. The treatments below assume a pixel-perfect UI source where contain-fit is non-negotiable.
## Anatomy
```
.frame-shot.r-{ratio}.corners-{sq|sm|md}.shadow-{none|soft|ed}.bg-{paper|grid|dot|grey-1|ink}.inset-{none|sub|bal}
└─ (object-fit: contain by default)
```
Optional wrapping:
```
.device-browser
└─ .frame-shot.r-16x10.bg-paper
└─
.device-phone
└─ .frame-shot.r-3x4.bg-paper
└─
```
## Parameters
Pick six values before writing the markup. Treat this like the M16 cover decision tree — pick once, don't fiddle mid-build.
### 1. `r-*` ratio (required, matches slot)
| Class | Use |
| ---------- | --------------------------------------------------------- |
| `r-16x10` | Default for app / web shots, looks like a real window |
| `r-16x9` | Landscape video / dashboard / wide chart |
| `r-4x3` | Classic desktop window, legacy app |
| `r-3x2` | DSLR-style — only if the source is photographic UI mockup |
| `r-1x1` | App icon / square widget |
| `r-3x4` | Mobile portrait shot (pair with `.device-phone`) |
| `r-21x9` | Multi-monitor / ultra-wide / WeChat hero |
### 2. `corners-*` (style-locked default)
- **Swiss** default: `corners-sq`. Use `corners-sm` only if the slot has surrounding shadow or chrome.
- **Editorial** default: `corners-sm` (6 px). Bump to `corners-md` (14 px) for "cutout" feel on paper.
Never go above 14 px — anything bigger reads as iOS marketing.
### 3. `shadow-*` (style-locked default)
- Swiss → `shadow-none` 90% of the time. `shadow-soft` only on screenshots that float on `bg-grid` / `bg-dot`. `shadow-ed` adds a `1px` outline as part of the shadow — reserve for hero shots.
- Editorial → `shadow-soft` on `bg-paper-2` is the warm default. `shadow-ed` for hero shots.
### 4. `bg-*` (the screenshot "stage")
| Token | Swiss role | Editorial role |
| ------------ | ------------------- | ---------------------- |
| `bg-paper` | Default plain stage | Same |
| `bg-paper-2` | n/a | Default warm stage |
| `bg-grey-1` | Default plain stage | n/a |
| `bg-grid` | Engineering / data | Field-notes engineering |
| `bg-dot` | Subtle structure | Subtle structure |
| `bg-ink` | Dark-mode UI shot | Dark-mode UI shot |
Backgrounds are **never** accent-coloured. If the screenshot needs an accent emphasis, add a `.t-cat` chip or `.kicker` next to it — don't tint the stage.
### 5. `inset-*` (padding between shot and stage)
- `inset-none` — image fills the frame. Use when the screenshot itself already has window chrome.
- `inset-sub` (Swiss 20 px / Editorial 24 px) — default. Lets the stage breathe.
- `inset-bal` (Swiss 48 px / Editorial 56 px) — when the shot is busy and needs to feel calm.
### 6. `fit-cover` (override)
Default is `object-fit: contain` — this is the whole point of `.frame-shot`. **Only** add `.fit-cover` when:
- The slot is a hero where exact pixels of the source don't matter (e.g. a code shot used as a background pattern).
- The user explicitly says they want the shot cropped.
## Device chrome
Two wrapper classes ship with the seeds. They wrap a `.frame-shot`:
### `.device-browser`
Adds a 32–36 px chrome bar with traffic-light dots. Use for web / desktop app captures.
```html