Text overlays are baked into the output image. Use them for social cards, app store screenshots, launch visuals, and image sets where the copy should travel with the asset.

Structured title fields

json
{ "url": "https://example.com", "background_preset": "midnight", "title": "Analytics without setup work", "subtitle": "A cleaner launch image generated from the live product", "badge": "New", "title_position": "above"}

Free-form text box

Use text_enabled for precise positioning.

json
{ "url": "https://example.com", "aspect_ratio": "1:1", "background_preset": "ember", "text_enabled": true, "text_content": "Launch assets from a URL.", "text_x": 0.08, "text_y": 0.72, "text_size": 72, "text_weight": 800, "text_gradient": "linear-gradient(180deg, #ffffff 0%, #fde68a 100%)", "text_shadow": "0 4px 24px rgba(0,0,0,0.35)", "text_max_width": 0.74}

Autofit

Autofit lets you keep a template stable when copy length varies.

json
{ "text_enabled": true, "text_content": "A longer line of launch copy that still needs to fit", "text_autofit": true, "text_size": 96, "text_fit_min": 32, "text_max_width": 0.78, "text_box_h": 0.28, "text_vertical_align": "middle"}

Text guidance

Use caseRecommended approach
Blog OG imagetext_enabled with square or 16:9 ratio.
App store screenshottext_enabled, text_autofit, and fixed positions across all screenshots.
Product herotitle and subtitle above or below the frame.
ChangelogShort badge plus a precise element capture.

Keep overlay copy short. The screenshot should remain the subject; text should frame the image, not replace the page content.

Ask a question... ⌘I