style_id, and generate with it immediately. The references can come from anywhere — other generators, branding materials, or existing assets.
V4 Styles models always require a style. Every request must supply either
style_id or style reference images. A request with neither is rejected.Models
Like the rest of the V4 line, V4 Styles is available in standard (1K) versions for everyday work and fast iteration, and Pro (2K) versions for print-ready assets and large-scale use. Both share the same style behavior.
How to call it
There are two ways to work with the model. Use the two-step flow when a style is reused across many requests — the typical case for brand and campaign work. Use the one-step flow to go straight from references to an image.Option 1: create a style, then generate
1
Create the style
Upload your reference images to
/v1/styles. The response returns a style_id you can reuse indefinitely.2
Generate with that style_id
Pass
style_id plus a V4 Styles model to /v1/images/generations. Repeat for every asset in the set.Option 2: attach style references to the generation
Skip style creation and attach the references to the generation call itself. The server creates a private style from them, applies it, and returns the resolvedstyle_id so later requests can reuse it.
Reference images
A single reference is enough. Adding more changes the result in a predictable way: similar references sharpen the match, varied references widen the range.
Unlike most models, which only work reliably with references created inside that same model, V4 Styles accepts references from anywhere: other generators, branding materials, or existing assets. There is no requirement that a reference was produced by the model you are generating with.
The Create style endpoint also accepts
image_weights: per-image weights, one per uploaded image, to bias the style toward specific references.
Style match
Every style stores amatch value, set with the match parameter at style creation, that controls how closely generated images follow the style:
precise(the default) — follows the style meticulously, holding every detail: rendering technique, color, composition, and lighting.flexible— matches the general vibe, giving the model slightly more liberty — for when the mood matters more than the exact blueprint.
style_match in a generation request overrides the stored value for that style. See Style match for details.
Example
Two generations with the same style references — oneprecise, one flexible:
Pro or Vector generation
Style-consistent generation is not limited to the standard raster model. The line includes Pro (2K raster) and Vector (SVG) variants, and a style applies the same way on each of them: userecraftv4_styles_pro for print-ready 2K raster assets, and recraftv4_styles_vector or recraftv4_styles_pro_vector for editable SVG output.
Example
Generating an SVG with the Pro Vector model and style references:Supported operations
- Generate image — a style is always required.
- Create style —
recraftv4_stylesis the default model when nomodelis specified.
Pricing
Generation and style creation are billed separately. Among the models that support styles, the V4 Styles line has the most attractive pricing for style-consistent generation.
API units are purchased in advance: $1.00 buys 1,000 units.
Composite billing on attached references. When you attach style references to a generation instead of passing a
style_id, the style creation is charged once on top of the per-image generation cost. The credits field in the response is the sum of both.
Worked example. A style created once, then a 10-image set generation:
Reusing that
style_id on later sets costs generation only, with no further style-creation charge.
Styles on other V4 models
Styles are not limited to the V4 Styles models. Every V4 and V4.1 model accepts astyle_id or attached style references on /v1/images/generations. Generation stays at that model’s own price: applying a style does not change it. Style creation is billed separately at $0.005 per request either way.
The difference is that V4 Styles is purpose-built for style consistency and always requires a style, while the other V4 models treat a style as an optional input.
See Pricing for generation prices of the other models.
Errors and rejections
Related
Getting started
Authentication and your first generation request.
Endpoints
Full parameter reference for generate image and create style.
Styles
How styles work across models: custom styles and style match.
Pricing
Complete API unit charges across every model and operation.