Use width and height in multiples of 64 so a multi-provider image API can normalize sizes without silent crop chaos.
“A light coastal pavilion hovering over reflective water, pale stone planes, blue glass, calm sun, minimal architectural render”
FLUX Dev · premium · 960 × 1472Normalize before the provider call
A routed API cannot rely on the most permissive model in the fleet. One provider may accept a multiple of eight while another is safer at 64. Enforcing the stricter shared rule at the public boundary prevents a request from succeeding on the primary and failing only when a fallback is needed.
RenderRoute checks bounds and snaps each side to the nearest multiple of 64 when auto adjustment is enabled. The response includes requested and actual dimensions plus a dimensions_adjusted flag. Clients that require exact sizing can disable adjustment and receive a validation error instead.
def nearest_64(value: int) -> int:
return ((value + 32) // 64) * 64
assert nearest_64(1000) == 1024
assert nearest_64(1500) == 1472Name presets by product use, not by arbitrary numbers
A preset should carry composition intent. ‘Portrait editorial’ communicates more than 960×1472 and lets the design system define safe areas, crop behavior, and cost. Keep the raw dimensions available for advanced clients, but steer ordinary users toward tested presets.
Generate in the final aspect ratio whenever possible. Cropping can remove a subject, hands, product details, or planned text space. If several channels need different shapes, generate or art-direct each shape rather than assuming one master crop will work everywhere.
| Preset | Aspect | Good starting use |
|---|---|---|
| 1024 × 1024 | 1:1 | Tiles and catalog concepts |
| 960 × 1472 | 15:23 | Portrait and mobile editorial |
| 1472 × 960 | 23:15 | Landscape concepts and banners |
| 768 × 1344 | 4:7 | Lower-pixel vertical drafts |
Treat dimension changes as a cost event
A small-looking change in each side can create a meaningful change in total pixels. Record final dimensions, not only requested dimensions, when estimating cost. At scale, silent snapping without metadata can distort customer credits and provider comparisons.
The included cost calculator scales the operator’s portrait benchmark by pixel area as a planning estimate. Replace that approximation with provider-reported cost where available and model-specific measurements where billing is not linear.
- Calculate pixel area after normalization
- Multiply by image count
- Keep fast and premium curves separate
- Benchmark the actual presets offered in the UI
Do not confuse generation size with delivery size
Generate an asset suitable for editing and retention, then create responsive delivery variants through an image CDN or processing pipeline. Sending a 1472-pixel image to every mobile card wastes bandwidth and harms page experience.
Use width and height attributes in HTML to reserve layout space, modern compressed formats, meaningful file names, and alt text that describes the image’s purpose. The marketing site uses responsive local artwork, explicit dimensions, and modern compressed image formats.
Questions about AI image dimensions multiples of 64
Are multiples of 64 always required by every model?
No. Some models accept smaller increments. RenderRoute uses 64 as a conservative shared rule across a changing provider fleet.
What happens to 1000×1500?
With auto adjustment it becomes 1024×1472. The response reports both requested and final values.
Can I require exact dimensions?
Yes. Set auto_adjust_dimensions to false; incompatible sizes return a validation error before any provider call.
Is 960×1472 a standard aspect ratio?
It is a practical 15:23 portrait preset chosen for this product and benchmark, not a universal standard.