Render the ODD first
Open the drawing in an ODF-capable application and export the intended page or artwork as PNG, JPG, WebP, or another browser-readable image.
Free ODD to AVIF guidance
Fileverses cannot decode an ODD upload directly. Render the OpenDocument drawing to a browser-readable raster image first, then use this free online page to request an AVIF canvas export at quality 0.7 when your browser supports AVIF encoding.
Files stay in this browser
All conversion runs on-device
About this converter
ODD is an OpenDocument Drawing container, while this browser converter accepts decodable image files rather than ODD packages. The practical path is render the intended drawing in an ODF-capable application, inspect the resulting raster image, and then encode that raster as AVIF here. That changes the drawing into pixels; it does not retain its document objects, pages, or editing structure.
How it works
Open the drawing in an ODF-capable application and export the intended page or artwork as PNG, JPG, WebP, or another browser-readable image.
Choose that raster image here. Do not upload the .odd file itself: the browser converter does not decode it.
Select AVIF when it is available, convert, then test the download in the browser, CMS, or application that will receive it.
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 AVIFThe page explains that ODD packages need external rendering instead of pretending they can be decoded in the browser.
Supported raster pixels are encoded locally through the browser canvas AVIF path at quality 0.7.
Test the rendered AVIF in its destination because AVIF support and encoder results can vary.
Good to know
The Fileverses page is free and online, with no account required, but it needs a rendered raster image rather than a direct ODD upload.
No. ODD is excluded from the browser-decoding path. Render the drawing externally to a browser-readable image first.
After you provide a supported raster image, its conversion runs in the browser rather than being sent to a conversion server.
The browser canvas encoder is requested at quality 0.7. The resulting file can vary by browser and source pixels.
No. The workflow exports rendered pixels, not ODD document objects, layers, or editable shapes.
No. File size depends on the externally rendered raster and the browser encoder, so compare the downloaded file for your use case.