Favicon Generator in the browser is not a generate
/free-tools/favicon-generator never spends a credit. Do not pay a model to do an in-browser file job.
/free-tools/favicon-generator never spends a credit. Do not pay a model to do an in-browser file job. The pack is six PNGs from one image, zipped on your machine. Nothing is uploaded. No account. No watermark. Generation is a different meter.
Versely has no free tier for models. Every generate draws credits. The free-tools surface exists because of that: utilities that never call a model, an API, or the network. Favicon is one of them. Sending a mark through an image model to “make icons” is how you spend the generation bill on a resize.
The favicon pack is a file job
One source image in. Six PNGs out: 16, 32, and 48 for tabs and bookmarks; 180 for Apple’s touch icon; 192 and 512 for a web app manifest. Non-square sources are centre-cropped to a square at each size, then scaled. The download is a ZIP of those six files. A multi-resolution .ico is a different format and is not generated here.
That is the whole product. Canvas and the File API, in the browser you already have. Disconnect the network and it still works, which is the proof it is not a generate.
Start from a square. If the full mark has to survive at 16px, design the icon on a square canvas first. A wide logo loses its sides at every size because the crop is centre, not “smart.” A model will not save a wide lockup you should have cropped yourself. It will invent a new lockup.
Generation is a different meter
What it costs is the credit surface: every job on Versely is billed in credits, but not by the same arithmetic — per second, per thousand characters, per megapixel, per tier, per job. Favicon is not on that list. It is zero, because no model runs.
The mix-up is treating “icon” as an image-model prompt. Posters and logos are a generate when you need a mark that does not exist yet. A favicon is a mark you already have, sampled to six sizes. If you do not have a mark, that is an image-model job first, on a square canvas, proofed at 100%, then this tool. Do not skip the file job and ask the model to emit six sizes. You will pay for six generations of a mark that drifts, and you still will not have the 180 / 192 / 512 set this ZIP already names.
Credits are for motion, lettering, voice, edit renders. They are not for packing PNGs.
What the ZIP actually contains
The filenames are the spec: favicon-16.png, favicon-32.png, favicon-48.png, apple-touch-icon-180.png, icon-192.png, icon-512.png. Serve those six and you have covered almost every place a favicon is requested. You still write the HTML and the manifest. The tool does not inject tags into your site and does not keep the image.
Transparency survives; the canvases export as PNG. JPEG would have to fill transparent pixels with a solid colour, which is why this tool does not offer JPEG.
If 16px looks like mush, the source is the problem, not the scaler. A detailed illustration will collapse in a tab. Simplify the mark, then run the pack again. That loop is free. Regenerating a “cleaner icon” on a model until a tab looks right is the expensive way to learn you needed fewer details, not more credits.
Use the generator when the mark is locked. Use a model when the mark does not exist. Do not use a model as a resizer.
FAQ
Does the favicon generator charge credits?
No. It never spends a credit. There is no account and no limit, because the work happens on your device. Image and video models on Versely do charge credits; this is not that surface.
Are my files uploaded?
No. The image is read into memory in your browser, cropped and scaled there, and offered back as a ZIP. Nothing is sent to a server. That is also why it keeps working offline.
Why these six sizes and not an .ico?
16, 32, and 48 cover tabs and bookmarks. 180 is the Apple touch icon. 192 and 512 are the sizes a PWA manifest asks for. A multi-resolution .ico is a different format and is not produced here.
Can I prompt a model for a 512 icon and skip this tool?
You can generate a mark. You should still pack it here. A single 512 PNG from a model is one file, not the six sizes the tab, the touch icon, and the manifest actually request.