Render and prepare the artwork
Export the chosen ODD page or artwork from an ODF-capable app as a browser-readable raster image. Check its composition before scaling it into icon sizes.
Free ODD to ICNS guidance
This free online ODD to ICNS workflow begins with an external render because ODD packages are not decoded in the browser. Upload a browser-readable image of the artwork, then create an ICNS container with six centered PNG entries; it is not an ODD-to-app-icon design service or a document conversion.
Files stay in this browser
All conversion runs on-device
About this converter
ODD stores OpenDocument Drawing content, but the icon encoder works from a browser-decoded raster image. Render and inspect the intended ODD artwork in an ODF-capable application first, then upload that image here. The resulting ICNS file contains centered PNG entries at six fixed sizes, which scales and pads the rendered image rather than selecting ODD content, cropping it, or building a macOS application bundle.
How it works
Export the chosen ODD page or artwork from an ODF-capable app as a browser-readable raster image. Check its composition before scaling it into icon sizes.
Upload the raster export rather than the .odd file. The converter centers it with contain scaling and transparent padding in each icon square.
Create the ICNS file and test it in the macOS or development workflow that will receive it; this page does not install or configure an app icon.
Made for real pipelines
Convert without uploading your assets. Switch outputs anytime — web, print, icons, and document targets from the same batch.
Prepare ODD artwork for ICNSThe route requires an external raster render instead of claiming to decode OpenDocument Drawing packages.
The ICNS output contains centered PNG entries at 16 through 512 pixels for a defined icon-family handoff.
Contain scaling with transparent padding preserves the rendered image proportions instead of inventing a square crop.
Good to know
The page is free and online with no account required, but you must render the ODD drawing to a supported image before creating ICNS.
No. ODD packages are outside the browser image decoder. Render the intended artwork with an ODF-capable application first.
The encoder packages PNG entries at 16, 32, 64, 128, 256, and 512 pixels.
No. It uses contain scaling and transparent padding to center the rendered image in each square; it does not automatically crop or remove a background.
The PNG icon entries can carry transparency from the browser-decoded rendered image. The workflow does not create transparency or remove a background.
No. It creates an ICNS container only. Add and validate it in the relevant macOS or development workflow yourself.