Recraft V4.1 API pricing is best planned as a task matrix, not a single image-generator price. The official Recraft API pricing page and Recraft API pricing docs list separate costs for raster generation, vector generation, editing, background removal, vectorization, upscaling, and erase operations. This guide turns those units into practical brand, product, and catalog asset planning numbers.
The current official pricing model uses prepaid API units, with 1,000 API units priced at $1. Recraft V4.1 raster is listed at $0.04 per image, V4.1 Pro raster at $0.25 per image, V4.1 Vector at $0.08 per image, and V4.1 Pro Vector at $0.30 per image. Editing services add their own units, so a production budget should separate first-pass generation, cleanup, background work, vector output, and final upscale.
Recraft V4.1 API cost matrix
| Task | Official planning unit | 100 assets or requests | 1,000 assets or requests | Best-fit workflow |
|---|---|---|---|---|
| Recraft V4.1 raster | $0.04/image | $4 | $40 | Everyday campaign images, social variants, and fast creative iteration. |
| Recraft V4.1 Pro raster | $0.25/image | $25 | $250 | Higher-resolution product, ad, and print-oriented final assets. |
| Recraft V4.1 Vector | $0.08/image | $8 | $80 | Editable SVG-style icons, simple illustrations, and brand systems. |
| Recraft V4.1 Pro Vector | $0.30/image | $30 | $300 | Complex vector compositions, detailed brand artwork, and production libraries. |
| Image-to-image, inpainting, replace or generate background | $0.04/request | $4 | $40 | Revision passes after a first generated or uploaded image. |
| Background removal | $0.01/request | $1 | $10 | Catalog cleanup, marketplace cutouts, and product-image prep. |
| Vectorization | $0.01/request | $1 | $10 | Converting approved raster concepts into editable vector routes. |
| Crisp upscale | $0.004/request | $0.40 | $4 | Low-cost final polish when the composition is already accepted. |
| Creative upscale | $0.25/request | $25 | $250 | Higher-touch refinement where detail and re-rendering matter. |
| Erase region | $0.002/request | $0.20 | $2 | Small object cleanup, stray-text fixes, and composition repair. |
100 and 1,000 asset scenarios
| Scenario | Planning mix | Estimated API spend | Budget note |
|---|---|---|---|
| Social ad variant set | 100 V4.1 raster outputs plus 25 edit passes and 25 crisp upscales | About $5.10 | Use this when fast variation matters more than print-ready resolution. |
| Product catalog cleanup | 1,000 background removals plus 300 erase-region fixes and 300 crisp upscales | About $11.80 | Cheap per request, but QA and marketplace resizing can dominate labor cost. |
| Brand icon library | 250 V4.1 Vector outputs plus 100 vectorization passes | About $21 | Plan extra review for consistency, line quality, and export cleanup. |
| Premium launch creative | 100 V4.1 Pro raster outputs plus 30 creative upscales | About $32.50 | Useful for finals, but first draft exploration should usually happen on cheaper routes. |
| Complex vector campaign | 100 V4.1 Pro Vector outputs plus 40 edit passes | About $31.60 | Best for detailed, scalable compositions where editable SVG matters. |
Direct Recraft API versus wrapper route
Recraft V4.1 docs are the right source for model-family scope and the official Recraft pricing pages are the right source for direct API billing. Runware’s Recraft V4.1 Pro API docs and Runware pricing are useful as wrapper-route context because some teams want one media API for multiple models. Keep the numbers separate: wrapper convenience, routing, output delivery, and included cost fields can change the operational decision even when a listed per-image model price looks similar.
| Decision point | Direct Recraft API | Wrapper/API route | Makefun planning angle |
|---|---|---|---|
| Primary source of truth | Recraft API pricing and docs. | Wrapper model docs and pricing page. | Use direct pricing for Recraft cost claims; use wrapper pages for routing context only. |
| Model choice | Best when Recraft is the known production route. | Best when teams compare Recraft with FLUX, Krea-style, or other image APIs. | Compare final approved asset, not raw generation price alone. |
| Operations | Fewer platform layers. | Potentially easier multi-model testing and delivery options. | Budget wrapper markup, failure handling, and integration time. |
| Asset governance | Keep source prompts, API task type, and approved output IDs. | Also log wrapper model ID, delivery method, and cost response fields. | Store approved outputs permanently before campaign use. |
Hidden cost drivers
- Raster versus vector: vector output costs more, but it may reduce downstream design labor when SVG editing is required.
- Pro model tier: Pro routes are for higher-resolution or more polished finals, not every draft.
- Revision loops: inpainting, image-to-image, background replacement, and erase requests can turn one approved asset into several paid operations.
- Brand style setup: the real cost includes prompts, style references, color checks, typography review, and approval time.
- Failed generations: estimate by approved asset, not raw attempt count.
- Upscale choice: crisp upscale is cheap final polish; creative upscale is a higher-cost quality pass.
- Wrapper markup: a unified API can simplify routing but should be measured against exact model, output, delivery, and retry assumptions.
Workflow template for brand teams
- Sort the brief into raster generation, vector generation, edits, background cleanup, and upscale buckets.
- Pick draft and final routes separately: cheaper raster for exploration, Pro or vector only when the output requirement justifies it.
- Estimate first-pass attempts, revision rate, QA reject rate, and final approved asset count.
- Run a small brand-consistency pilot before batching hundreds of outputs.
- Store approved outputs in permanent hosting and keep prompt, source, and license notes for later refreshes.
Makefun workflow fit
For Makefun readers, Recraft is most useful to compare against adjacent image and product-asset routes such as FLUX 2, FLUX 2 versus Nano Banana Pro, Krea 2 image workflows, and cloth swap. Do not choose a tool on price alone. Match the task type, output format, revision burden, and final approval requirements before deciding whether direct Recraft API, a wrapper route, or a managed Makefun-style workflow is the better fit.
FAQ
Is Recraft V4.1 API pricing one flat image price?
No. Raster, vector, Pro, Pro Vector, editing, background removal, vectorization, upscale, and erase operations have different units, so production budgets should be task based.
When should a team pay for vector output?
Use vector routes when the approved asset needs editable geometry, scalable icons, print layouts, or design-system reuse. If the output is only a social image or catalog photo, raster plus targeted edits may be enough.
Is Runware pricing the same as Recraft official pricing?
No. Treat Runware as a wrapper/API route with its own pricing page and platform behavior. Use official Recraft sources for direct Recraft API cost claims.
