Plans and limits

No sign-up is needed to start: GET /chart works without authentication for up to 100 renders per month per IP. A free account adds API keys and 500 renders per month.

A render is one chart output Szum produces when a request reaches the origin: an API image, editor export, saved image, fresh embed response, MCP preview, or MCP image. CDN cache hits, local editor previews, Figma canvas renders, validation, saving, and client-side interactions do not count. Guest MCP previews are complimentary; opening their static image uses the separate anonymous MCP image allowance.

Feature comparison

Feature details

API keys – Unauthenticated GET /chart requests are limited to 100 renders per month per IP. Sign up for a free account to get API keys and 500 renders per month. See Authentication.

Saved charts – Any signed-up account can POST /api/charts to save a chart document server-side and get back two short URLs: szum.io/c/{id} for a rendered image (drop in emails, Markdown, Slack – anywhere <img> works) and szum.io/e/{id} for an interactive HTML embed (drop in any <iframe>). Only cache-miss loads cost a render against the creator’s monthly quota; CDN cache hits are served from the edge for free. Each stored document is capped at 64 KB, and your plan’s saved chart storage is listed in the table above. Every plan keeps each chart’s version history, counted in that storage; when it runs out, the oldest earlier versions make room, so history never blocks publishing. Saved charts stay live on any plan – the storage budget only limits new saves and larger updates. Delete one with DELETE /api/charts/{id}, or all of them from Account → Settings. See Saved charts.

Theme customization – Creator, Pro, and Team can override a curated theme’s typography, spacing, palette, and other exposed properties. See all theme properties.

Branding – Free and keyless renders carry a small “Made with Szum” credit – baked into static images (reserving a thin bottom band, see Sizing), and a clickable link on interactive embeds. Creator, Pro, and Team renders omit it. Attribution is resolved from the rendering account’s plan rather than authored in the chart document. Charts inserted by the Figma plugin are never branded, on any plan.

Team – One flat price per workspace with unlimited members. The workspace shares its renders and storage, and adds shared themes, chart rules, allowed embed domains, and filtering charts by author and source. See Team workspaces.

Support – Email support comes with Creator, Pro, and Team, and priority email support with Pro and Team.

Overage billing – Pro and Team can opt in to overage billing from the dashboard. Once enabled, renders beyond the plan’s included allowance continue at $1 per 5,000, billed at the end of the billing period. You’ll receive email notifications at $1, $5, $10, $25, $50, $100, $250, $500, $1,000 of overage, then every $1,000.

Rate limits

When you exceed your monthly render limit (and overage billing is not enabled), the API returns 429 Too Many Requests:

{
  "error": {
    "code": "limit_reached",
    "message": "Monthly render limit exceeded (25000/25000). Enable overage billing at https://szum.io/studio/billing.",
    "retryable": true,
    "details": { "retryAfter": 86400 }
  }
}

This applies to cache-miss loads of /c/ or /e/ too – they return 429 when your render quota is exhausted and overage is off. CDN cache hits continue to serve while their entries are warm (~24h max), for free. Limits reset on the 1st of each month (UTC).

See Errors for the shared error envelope. For an exhausted monthly allowance, retryAfter gives the seconds until the allowance resets; the value above is illustrative. Wait for that reset or change the account’s allowance before retrying. This is distinct from a temporary burst rate limit.

Need more?

Need a custom SLA or volume pricing? Let’s talk.