Learn · 3 min read · updated 2026-10-24

Printful's mockup API: rate limits and how to cache

If your customers design something live, Printful's mockup generator can't keep up with them. Here's the limit, and the two-tier setup we planned around it.

The limits

• 2 mockup task requests per minute for a new account. A request over the limit gets HTTP 429 with a Retry-After header.
• 10 per minute once the store has at least $10 of fulfilled orders.
• 20,000 generated files per day. One task can return many files (colour × style × placement), so this one rarely binds first.
• Async. You create a task, then poll it or wait for the webhook that says the task finished.
• No fee listed in the API docs for generating mockups. The generated image links are temporary, so copy anything you want to keep to your own storage as soon as the task finishes.

Tier 1: the live preview never calls the generator

Printful's catalog API also exposes mockup templates: the blank product photos and where the print area sits on each one. Printful's docs say these can be used to make your own mockups without the generator. Fetch them once per product from the catalog endpoint, which falls under the general API limit rather than the 2 a minute mockup limit, copy the images to your own bucket, and in the browser draw the design over the template's print area.

That preview is instant, free and has no rate limit, because nothing leaves the page. Each template says whether its photo sits over or under the design, so follow that rather than guessing. Keep a flat vector mockup as the fallback if a template is missing.

Tier 2: real renders, queued and stored

Use the generator only where an exact Printful render pays for itself, and treat it as a slow, shared resource:

• Key every render by a hash of the print file plus product, colour and style. If the key exists in storage, serve it and never call Printful.
• Create the job once. A create-only record per key stops double clicks and webhook retries from creating duplicate tasks.
• Queue the calls with a dispatch rate under the limit (one every 35 seconds leaves headroom at 2 a minute) and concurrency of one. On a 429, fail the attempt so the queue backs off and honours Retry-After.
• Finish on the webhook, with a delayed poll as the fallback, then download the file to your storage and mark the job done.
• Cap yourself at a daily number far below 20,000, so a bug can't spend the account's quota.

Where real renders pay off

After a paid order (the receipt and the thanks page can show the actual printed design on the actual shirt), and for your own catalog and social images, which you render once in a batch. A see it for real button on a live editor doesn't fit under 2 a minute shared across every visitor; revisit it at 10 a minute with a per-visitor daily cap.

If you need lifestyle photos (models, rooms), paid mockup APIs like Dynamic Mockups render your own photo templates (its free plan is a small, watermarked trial); Placeit has a big library but no public API.

Questions people ask

Sources

1. Printful API v2 documentation (mockup tasks, rate limits, mockup templates)
2. Printful API documentation
3. Dynamic Mockups pricing

Checked 2026-10-24. Policies and rules change; follow the source before you rely on a detail. This is general information, not legal advice.