Backgrounds define the canvas behind the captured page or device frame.

Named presets

json
{ "url": "https://example.com", "background_preset": "aurora"}

Available presets:

PresetTypical use
auroraLaunch visuals, social posts, playful product shots.
sunsetWarm editorial images.
oceanCalm SaaS and docs visuals.
midnightDark product hero images.
arcticClean light screenshots and directories.
duskRich purple/blue gradients.
forestGreen, product-led compositions.
emberHigh-contrast release assets.
customPair with custom gradient or color controls.

Solid color

json
{ "url": "https://example.com", "background_style": "solid", "background_color": "#F6F3FF"}

Custom gradient

json
{ "url": "https://example.com", "background_style": "gradient", "background_gradient": "radial-gradient(120% 120% at 50% 0%, #ffffff 0%, #ede9fe 45%, #7c3aed 100%)"}

Image background

Use background for hosted ScreenFramed backgrounds. The API expands the reference to a render-sized image variant for faster composition:

json
{ "url": "https://example.com", "background": "fractal-glass-gradients/fractal-glass-34", "shadow": "float", "padding": 80}

For your own image, pass a public URL:

json
{ "url": "https://example.com", "background_image_url": "https://assets.example.com/backgrounds/launch.webp", "shadow": "float", "padding": 80}

background_image_url overrides background when both are provided. Use a public image URL with stable caching. Large custom background images can increase render time.

No background vs transparent

StyleResult
background_style: "none"No decorative background; the canvas uses the basic composition treatment.
background_style: "transparent"Alpha channel is preserved in PNG or WebP output.

Transparent output:

json
{ "url": "https://example.com", "selector": ".product-card", "background_style": "transparent", "output": { "format": "png" }}

Transparent renders cannot use background, background_preset, or background_image_url, and JPG cannot preserve transparency.

Ask a question... ⌘I