Every screenshot both stores want, from one design.

No. A preset covers the layout, colour and typography of a whole set in one click, and the pre-flight tells you in plain words when something is off: text that does not fit, a badge over the safe area, a subtitle that will not read against the background. What is left is choosing the words, which is the part only you can do anyway.

One sitting, and most of it goes on the words rather than the layout. A preset resolves the design of a whole set in one click, so what is left is dropping the captures in, writing a headline and a subtitle per screen, and ticking the sizes and languages you want in the plan. The four to six hours this usually costs are artboard hours — duplicating, resizing, re-exporting, fixing the one file that came out wrong — and those are the ones that go away. Every release after the first is a capture swap and a download.

The captures come from wherever you already take them: a simulator, an emulator, a real phone, a tablet. PNG or JPEG, up to 12 MB each, at whatever size they came out — you do not crop or resize anything first, because the frame decides how much shows and you zoom and pan the capture inside it. The editor itself is a web page, so it runs the same on macOS, Windows and Linux, and you can build a full App Store set on a machine that is not a Mac. What it cannot do is take the screenshot of your app for you.

No, and this is the part that usually costs the most. The copy for every screen, every block and every language lives in one grid; you can send it out as CSV or XLIFF and import what your translator returns. If your translator is an assistant you already pay for, the same grid hands you the prompt and the JSON to paste into it — we call no model ourselves, and what comes back enters through the same import. A long translation shrinks its own text block until it fits the lines you allowed, so the German headline does not force you to redo the layout. If your app is localised too, you can drop a different capture on a single language and the others keep theirs. Pre-flight then runs over every language at every size, not the one on screen.

You open the project, swap the captures, and export. The layout, the copy, the languages and the variants are all still there, so a release turns into a capture swap and a download instead of the same afternoon again. If you are starting a different app, you can save the look you built and start that one from it — everything travels except the copy, which is deliberate.

No, and be suspicious of anything that says it does. The check reads the file: dimensions, format, alpha channel, how many assets the listing takes, whether the text fits and whether it reads against the background. Whether a reviewer objects to what a screenshot says or shows is content and policy review, it is a person on their side, and it stays your call. What we remove is the technical rejection, which is the one that costs you a day and tells you nothing.

Sizes, formats, counts and severities live in one file, each with the date it was last verified and a link to the store documentation. When one changes, the validator and the size pages on this site change with it, and the change shows up on the rule changes page with what it costs you. Every paid plan gets those updates, and the lifetime licence keeps getting them for as long as the product ships.

No. You choose what goes in the plan, and the export renders exactly that. Both stores take fewer sizes than people assume — Apple asks for the largest display of each family it supports and scales the rest down itself, and Play checks the shorter side, the longer side and the ratio rather than one exact pair of numbers. The size pages on this site say which one each store lists first, so you can ship the short list and be done.

In your browser. The drawing, the PNG encoding and the ZIP all happen on your machine, which is why an export costs us nothing to run and why the price can be a one-off instead of a subscription that pays for a render farm. Your project file and the captures you upload are stored on our server so you can pick the app back up on another machine; the rendered assets never are.

The entire editor — every preset, frame, background and font, no watermark, no timer — one app saved to your account, and one real exported file at the size and in the language you choose. Not a preview, not a sample: the same file the paid export writes, so you can open it, zoom in, and put it next to what you would have made by hand before you decide anything. What a plan buys is the rest of the set.

Yes. Every paid plan covers commercial use, work you hand to a client included, and holds up to 100 apps at a time with unlimited exports from each. There is no per-app and no per-seat charge, so one licence covers every app you ship this year and every app you ship for somebody else.

Identical, down to the last feature: same sizes, same languages, same A/B variants, same unlimited exports. The only thing the price buys is how long the access lasts and how long you keep getting rule updates. There is no feature held back to make you upgrade, because the export runs on your machine and costs us nothing either way.

Paddle. They are the merchant of record for the sale, which means the charge on your statement is theirs, the invoice is theirs, and the VAT or sales tax your country asks for is collected and paid by them. Nothing about your card ever reaches us. In practice: you pay one price, you get a proper invoice, and neither of us has to think about tax registration.

Write to us within 14 days of the payment and you get it back, including the lifetime licence. We would rather refund you than have you keep a tool you do not open. Paddle handles the money, so the refund goes back to the card that paid.

Cancel from your account page: the button and a confirmation, no retention script and nobody to talk to. The plan runs to the end of the period you already paid for and then stops; nothing else is charged, and you can undo it any time before that date. Your apps, your uploads and everything you already exported stay exactly where they are. Coming back is buying a plan again, not rebuilding anything.

Chrome or Edge 80+, Firefox 113+, or Safari 16.4+, on a window at least 1280px wide. It leans on the FontFace API and Pointer Events, and the canvas needs the room, so designing is a thing you do at a desk, once, and then repeat in a couple of minutes per release. On a narrower screen the app still opens a set to look at and downloads it; what needs the width is editing it.