Initializing... drag & drop files here
Supports: ODG
AVIF wraps AV1-coded images in the HEIF container structure: royalty-free, extremely efficient on photographic content, and now supported by every current major browser. An .odg is an OpenDocument Graphics drawing — the shapes, connectors and text frames LibreOffice Draw and Apache OpenOffice Draw store as XML inside a ZIP. This converter renders the Draw document page by page and encodes each render as an AVIF. Before you do that, it is worth knowing that AVIF's strengths and a flowchart's content are close to opposites, so this page leads with the comparison rather than the button.
| Property | AVIF | WebP (lossless) | PNG | JPG |
|---|---|---|---|---|
| Underlying coding | AV1, lossy by default | Lossless | Lossless | Lossy DCT |
| Licensing | Royalty-free | Royalty-free | Royalty-free | Royalty-free in practice |
| Hard edges and small text | Good at high quality, soft at low | Exact | Exact | Weakest of the four |
| Transparency | Yes | Yes | Yes | None |
| Typical size, photographic artwork | Smallest | Large | Largest | Small |
| Typical size, flat diagram | Small | Often smallest | Moderate | Small but degraded |
| Browser support | 94.65% per caniuse — Chrome 85+, Firefox 93+, Safari 16.4+, Edge 121+ | Universal in current browsers | Universal | Universal |
| Desktop tool support | Still catching up | Good | Everywhere | Everywhere |
AVIF's advantage is largest on photographs and gradients. On a flat flowchart, lossless WebP will often be both smaller and exact, and PNG beats everything on compatibility. Pick AVIF when the destination asks for it, or when the drawing embeds photographic content that a lossless format would make enormous.
.odg onto the page or click "+ Add Files". The whole Draw document is read, so a multi-page file needs no splitting.A .odg is a page-layout document rather than a picture, so it does not go through an image converter directly:
| Stage | What runs | What comes out |
|---|---|---|
| 1. Read the drawing | LibreOffice Draw's PDF export filter (draw_pdf_Export) |
A PDF holding the document's own page size and object positions |
| 2. Render | Each PDF page rasterised at 300 DPI | One full-colour image per drawing page |
| 3. Encode | libvips writes each render as AVIF at the chosen quality | One .avif per drawing page |
At 300 DPI a US Letter page renders near 2550 × 3300 px and A4 near 2481 × 3507 px, which is generous for screen use — "Image resolution" is how you bring that down.
Sometimes. Its strength is compressing continuous tone, so a drawing full of photographs or gradients genuinely benefits. A flat flowchart is the opposite case: lossless WebP usually beats it on both size and fidelity, and PNG beats it on compatibility. Use AVIF when the destination specifically wants it, and keep the quality rung high when you do.
They share a container lineage. HEIF is the container standard, ISO/IEC 23008-12; HEIC is the common name for HEIF files whose images are HEVC-coded; AVIF holds AV1-coded images in the same family of boxes. The practical differences are the codec, the licensing situation and the software support — AVIF is royalty-free where HEVC is not, which is a large part of why browsers adopted it and not HEIC. Our ODG to HEIC and ODG to HEIF pages cover the other two.
Yes — the format carries an alpha channel and current browsers composite it correctly. Whether your drawing has transparency to keep is a separate question: if the Draw page has a background fill set under Page ▸ Page Properties ▸ Background, an area that looks empty is an opaque fill and will render that way. Older desktop applications may also ignore the alpha channel, so if the transparent background is essential and the recipient's software is unknown, PNG remains the safer hand-off.
No. AVIF's container supports image sequences, but that is an animation concept rather than a document one, and this route does not produce them. Each page becomes its own .avif, numbered in page order and delivered together. For all the pages in one openable file, ODG to PDF is the target designed for it.
No. Every raster target turns type into pixels, so nothing in an AVIF is selectable or searchable. Keep the .odg as your editable master, and use ODG to PDF or ODG to SVG when the text has to stay live.
Very High or Highest. AVIF at lower rungs smooths the high-contrast boundaries that make small type legible, and once smoothed it cannot be recovered. If the file is too large at Very High, reduce the pixel dimensions rather than the quality — a diagram survives downscaling far better than it survives aggressive quantisation.
.avif open in the software my colleague uses?In a browser, almost certainly: 94.65% of browsers support it, covering Chrome 85 and later, Firefox 93 and later, Safari 16.4 and later, and Edge 121 and later. Outside the browser it is less certain — many desktop image viewers, older design tools and some content-management systems still do not read AVIF. If you do not know what the recipient runs, PNG is the format that never needs explaining.
Not in a useful form. AVIF can hold Exif and XMP blocks, but the document properties an ODG stores — author, title, the object model itself — are not mapped into them by this conversion. Treat the image as a picture of the drawing and keep the .odg as the record.
They travel over an encrypted connection, are processed on our servers, and are deleted automatically a few hours later along with any output. Nothing is shared, published or reused, no account is required, and no watermark is applied. The ODG converter hub lists every other target for this source.