Skip to content
Kamply

Size spec

App Store in-app event sizes, 1920 × 1080 and 1080 × 1920 px

The two pieces of artwork an App Store in-app event asks for: a 16:9 event card and a 9:16 details page, each designed on its own canvas.

Kamply is a Mac app that builds posts, reels and store screenshots at these sizes. It works with your Claude Code or Codex subscription.

See finished workSee pricing

The frame, drawn to scale.

The boxes are the registry's numbers, placed in the frame's own pixels over a piece the engine made at this size.

A 16:9 App Store in-app event card: yoghurt, tofu, salmon, chicken and two eggs stacked on a dark field, each labelled with its protein in grams
The event card from NutriScan's protein challenge campaign. Made for NutriScan, a nutrition app. See the brief and the full piece

Event card

1920 × 1080 px

Padding
  • 72 px from every edge
  • 1776 × 936 px inside

The outer padding. Nothing that carries meaning sits inside it: no text, no button, no logo, no stat. A full-bleed photo or a background wash may cross it. The engine uses 72 px on a 1080 px wide frame and scales that for other widths, snapped to the 8 px grid.

Apple lays the event name and short description over roughly the bottom 35% of the artwork, per the registry's source note. The registry holds no box for that band, so none is drawn here.

A 9:16 App Store in-app event details image: five protein foods stacked, each labelled in grams
The details image from the same NutriScan campaign. Made for NutriScan, a nutrition app.

Event details

1080 × 1920 px

Padding
  • 72 px from every edge
  • 936 × 1776 px inside

The outer padding. Nothing that carries meaning sits inside it: no text, no button, no logo, no stat. A full-bleed photo or a background wash may cross it. The engine uses 72 px on a 1080 px wide frame and scales that for other widths, snapped to the 8 px grid.

What the engine checks at this size.

A post is not called done until it passes these. Each one is a check the engine runs on the finished post.

  1. Built at the exact pixels

    Each frame is an artboard at the registry size at 1x, so the export is the size printed above with no scaling step. Posts export as PNG or PDF.

  2. Text is measured against the boxes

    The engine's GRID check measures every text box on the rendered post and fails one that crosses the padding, leaves the safe box or enters a covered margin. Gaps and line heights sit on an 8 px grid. It judges posts whose brief was approved on or after 2026-09-07.

  3. Images are held to web weight

    Every image a post embeds is held to 3000 px on its long edge and 4 MB. A PNG with no transparency fails and ships as a JPEG.

  4. No image is stretched past its pixels

    An image drawn above 1.25 times its own pixels fails, because it reads soft at feed size. This check judges posts approved on or after 2026-10-05.

Where the numbers come from

Every size Kamply builds to sits in one registry file, and each entry names the platform spec it was read from. This is the source line the registry holds for this size, as written:

developer.apple.com/app-store/in-app-events: event card 16:9 1920×1080, details 9:16 1080×1920; Apple overlays name + short description on the bottom ~35%

Download Kamply for Mac

Bring one brief to the walkthrough.

We build the first direction with your brand during the walkthrough.

Akash, who built Kamply, replies with times. The walkthrough is free: he builds your first campaign direction on your brand, and you leave with the files.