Pricing

Pay for renders, not seats.

Cache hits are free. Unused credits roll over. Upgrade or cancel any month.

Free

Wire up the API, ship a campaign, see if it sticks.

$0forever
  • 1,000 renders / month
  • Public Unsplash + your URLs
  • 1 template
  • Community support
Start free
Recommended

Studio

For products in flight. Unwatermarked output, priority queue.

$29per month
  • 10,000 renders / month
  • No watermark
  • Priority API
  • Custom fonts + assets
  • Email support
Start the Studio trial

Scale

Dedicated infrastructure, SLAs, private deployments.

Customusage-based
  • Unlimited renders
  • Dedicated render nodes
  • SAML + audit logs
  • White-label CDN
  • SLA + on-call support
Talk to us

All plans use the same /v1/render endpoint. No feature gating on the API surface.

Questions

Likely already asked.

If your question is not here, mail hello@pixeldrive.pro. A real person answers within a working day.

  • Q.01

    What does it actually output?

    PNG by default. JPEG, WebP, and AVIF when the Accept header asks for them. Vector formats (SVG, PDF) are on the Studio plan.

  • Q.02

    How fast is a single render?

    Identical payloads return in 1–5 ms via the Redis cache. Cold renders average ~700 ms once we have warmed the browser pool. Bulk batches scale linearly with worker count.

  • Q.03

    Can I bring custom fonts and assets?

    Yes. Upload fonts in the editor or reference them by URL; same for image assets. Bring-your-own S3 bucket and CDN are supported on Studio.

  • Q.04

    How is billing handled?

    Credits are decremented only when a render actually runs. Cache hits are free. Unused credits roll over forever. You can upgrade, downgrade, or cancel any month.

  • Q.05

    Is there an API, or just the dashboard?

    The dashboard is a thin wrapper on the same API every customer uses. POST /v1/render for one image, /v1/jobs for batches, SSE on /v1/jobs/:id/stream for live progress.

  • Q.06

    Can we self-host?

    Scale-tier customers get a private deployment, either on our infra or theirs. We hand over the same container image we run, plus the Postgres + Redis schema and the Helm chart.