On-the-Fly Image Processing
Your Anycast CDN generates, caches and delivers image variants on request, while your origin keeps a single master file. Ask for a size in the URL and the edge does the rest.
Powered by the imgproxy processing server · Generated variants are cached at the edge like any other object · Engineer reply within 3 business hours
One image, every size
Your origin stores one file. The CDN generates, caches and delivers every variant from a query string on your own domain.
Source file, 1376 x 768
resizefit, width 800
resizefit, width 480
https://cdn.example.com/images/photo.jpg?preset=resizefill&width=1200&height=1000
How a request works
Ask for a variant in the URL. The CDN generates it once, caches it at the edge and serves every later request from there.
https://<cdn-domain>/<image-path>?preset=<preset-name>&<preset-parameters>
Host
Your CDN domain: the deployed server, domain or IP that answers the request.
Image path
Where the original lives on your origin or bucket. The master file itself is never modified.
Processing options
The preset name and its parameters, passed as query-string pairs separated by ampersands.
Example: ?preset=resizefill&width=800&height=600 returns a copy of the image that fills an exact 800 x 600 box. If the source has a different aspect ratio, it is scaled and then cropped, so the output always has the dimensions you asked for.
Four presets, one query string
crop
crop:$arg_width:$arg_height:$arg_gravity resize
resize:$arg_type:$arg_width:$arg_height resizefit
resize:fit:$arg_width:$arg_height resizefill
resize:fill:$arg_width:$arg_height Turn it on per location
Image Processing is switched on for a resource location, not for the whole account, so you decide where variants are generated.
Open your resource
In the user panel, open the CDN resource that serves your images.
Locations tab
Click Image Processing to enable the parameter. The configuration page unfolds right there.
Request a size
Add a preset and its parameters to any image URL on your CDN domain. The first request generates the variant, the rest are served from cache.
What 100 TB of delivered traffic costs
First 5 TB
- $25 for the whole tier
- This is also the monthly minimum
5 to 25 TB
- $90 for the next 20 TB
- 25 TB in total: about $115
25 to 100 TB
- $300 for the next 75 TB
- 100 TB in total: about $415
Questions buyers ask about on-the-fly image processing
BlazingCDN Image Processing resizes and crops images on request from a query string on your own CDN domain. The origin keeps one master file, and each generated variant is cached at the edge like any other object. Processing is included at no extra charge: you pay only for delivered traffic, from $5 down to $2.50 per TB.
How much does an image CDN with resizing cost at 100 TB?
BlazingCDN delivers 100 TB of processed images for $415 a month (as of October 2026), and Image Processing itself is included at no extra charge. You pay for delivered traffic only, not for each transformation or each variant.
The total follows progressive tiers. The first 5 TB bill at $5 per TB, which equals the $25 monthly minimum. The next 20 TB bill at $4.50 per TB, and the remaining 75 TB at $4.00 per TB. The rate is the same in the US, Europe and Asia, and BlazingCDN adds no request fees. The missing request meter matters for image-heavy pages, where a single product listing can trigger dozens of image requests. For example, a store serving 20 TB of thumbnails and product photos pays $92.50 a month, with resizing included. Variants are cached at the edge, so generation happens once and later requests are plain cache hits.
How does BlazingCDN resize images from the URL?
BlazingCDN resizes an image when the URL asks for it: a preset and its parameters in the query string tell the edge which variant to build. The first request generates the variant, the CDN caches it, and every later request is served from the edge.
A request has three parts. The host is your CDN domain. The image path points to the original on your origin or bucket, and the master file is never modified. The processing options are the preset name and parameters, joined by ampersands. For example, ?preset=resizefill&width=800&height=600 returns a copy that fills an exact 800 x 600 box. If the source has a different aspect ratio, the image is scaled and then cropped to those dimensions. Image Processing runs on the imgproxy processing server inside the Anycast CDN. The origin stores one file, such as a 1376 x 768 source, while the edge delivers every size you request.
Which presets does BlazingCDN Image Processing support?
BlazingCDN Image Processing supports four presets: crop, resize, resizefit and resizefill. Each preset takes its parameters, such as width and height, from the query string on your CDN domain.
The presets cover the common layout jobs. The resizefit preset scales an image to a target width while keeping its proportions, for example turning a 1376 x 768 source into an 800 or 480 pixel wide copy. The resizefill preset returns exact dimensions: the image is scaled, then cropped, so an 800 x 600 request always returns 800 x 600. The crop preset cuts out part of the image, and resize changes its size. Generated variants are cached at the edge like any other object, so repeat requests do not return to the origin. The documentation lists these four presets only. Buyers who need other transformations should confirm with an engineer, who replies within 3 business hours. Video transcoding is not offered.
Is BlazingCDN Image Processing a fit for a large product catalog?
BlazingCDN Image Processing fits a large product catalog when the main need is many sizes from one master file, because each variant is generated once and then cached. Processing is included at no extra charge, and delivery costs from $5 per TB down to $2.50 per TB (as of October 2026).
The model keeps storage simple. The origin holds one original per product, and the CDN produces thumbnails, listing images and zoom views on demand. Responsive layouts can request exact widths instead of storing five copies per photo. Limits are worth stating plainly. The documented toolset is four presets: crop, resize, resizefit and resizefill. BlazingCDN does not offer edge compute, so custom per-user image logic cannot run at the edge. For example, a marketplace with 200,000 listings can serve 480 and 800 pixel versions of each photo without storing them. Origin load stays low because the network averages a 96%+ cache hit ratio.
How do I turn on image processing in BlazingCDN?
BlazingCDN switches Image Processing on per resource location, not for the whole account, in three steps in the user panel. You decide exactly where variants are generated.
First, open the CDN resource that serves your images. Second, open the Locations tab and click Image Processing to enable the parameter, and the configuration page unfolds on the same screen. Third, add a preset and its parameters to any image URL on your CDN domain. The first request generates the variant, and the rest are served from cache. For example, enabling the feature on a /products/ location leaves /downloads/ untouched. A location is a rule set matched to an HTTP route, so different parts of one resource can get different delivery settings. New accounts get onboarding with an engineer in about one hour, and a 14-day testing period runs on real production traffic. Raw logs are available for $50 per month (as of October 2026).