Image Batch Resizer in the browser is not a generate
/free-tools/image-batch-resizer never spends a credit. Do not pay a model to do an in-browser file job.
/free-tools/image-batch-resizer never spends a credit. Do not pay a model to do an in-browser file job. A batch resize is arithmetic on pixels you already have. It is not a stills row, not an upscaler, and not a reason to open the generator.
Versely has no free tier for generation. Every model call costs credits, quoted before the charge. The free-tools surface exists because these jobs never touch a model, an API, or the network. The work runs in your browser on Canvas and the File API. Nothing is uploaded. That is why it can be free without contradicting the cost hub.
Canvas is not a model
The Image Batch Resizer takes many images, one target size or a platform preset, and packs the results as a ZIP. Same presets as the single-image resizer: TikTok / Reels / Shorts at 1080×1920, Story, Pinterest pin, Instagram square, 4:5 portrait, YouTube thumbnail, 1080p, 4K, X / LinkedIn. Those numbers are the sizes the platforms serve, not rounded guesses.
No account. No watermark. The tab can do this with the network off, because nothing is sent anywhere. That is also why a 40 MB ceiling exists per image: Canvas holds the decoded bitmap, and a huge file would crash the tab rather than fail cleanly. The tool takes up to fifty files in one pass. That is a memory cap, not a subscription cap.
If the job is "make this product look different," you are in a generate. If the job is "make these forty hanger shots 1080×1920," you are here.
Cover crops, stretch distorts, the ZIP keeps names
Fit is two modes. Cover scales until the box is full and crops the overflow — what you want for mixed photos going to a 1080×1920 slot. Stretch fills the box by distorting. There is no letterbox option, because that would add pixels that were not in the photo.
JPEG output re-encodes. The quality slider is the new JPEG quality, not a pass-through of the source tables. A second generation of JPEG is always a little softer than the file you started with. PNG sources stay PNG unless you pick JPEG. JPEG fills the canvas white before it paints, so transparency will not survive that pick.
The ZIP uses the original basenames with a new extension. You can drop the folder back over the source. That is the whole product: many files, one size, names intact, no upload.
Do not send the same folder through an image model "to sharpen for the feed." You will get forty new pictures and a credit bill. You will not get a resize.
Generation is a different meter
The cost hub is where generation arithmetic lives: per second, per thousand characters, per megapixel, per job. Credits roll over while a subscription is active. Every generate shows the figure before it charges. None of that applies here, because this tool never calls the meter.
Use the batch resizer when the pixels are already the pixels you mean — listing photos, screenshots, locked stills — and the only remaining job is the box they have to fit. Use a model when you need a new picture. Use image-to-video when a locked still has to move.
A resize that crops the product off the edge is still a crop you chose. Check cover against a 4:5 original going into 9:16 before you ZIP forty of them. The preview is the first file. If that crop is wrong, the other thirty-nine will be wrong the same way.
FAQ
Does the batch resizer use credits if I am logged in?
No. It never spends a credit, logged in or not. There is no account on the tool and no generate on the path. Credits are for models, caption burns, and editor exports — the jobs on /cost.
Will "cover" cut off my product?
Yes, if the source aspect is not the target. Cover fills the box and crops overflow. Stretch will not crop; it will squash. Pick cover for a feed slot. Shoot or crop the still yourself if the product has to stay fully in frame.
Why not run fifty stills through an image model at the target size?
Because that is fifty generates. You pay the image meter to re-invent pictures you already approved. The batch resizer is the file job. The model is the invention job. Keep them apart.
Is there a usage limit besides file size?
The pass caps at fifty images, 40 MB each, because the decode lives in the tab. There is no daily quota and no watermark. If you have more than fifty files, run a second ZIP. That is still not a generate.