ODP

Yes, PowerPoint has included built-in ODF import/export support since PowerPoint 2010, so a DAM can hand off an .odp asset without a conversion step or plugin. Newer Microsoft 365 builds add ODF 1.3/1.4 compatibility. However, complex animations, transitions, and certain master-slide formatting inherited from LibreOffice Impress can render differently in PowerPoint, so a DAM preview generated by one application should not be assumed identical to how the file opens in the other.

PPTX dominates overall because of Microsoft Office's market share, but ODP shows up regularly in DAM libraries belonging to public-sector bodies, universities, and organizations with open-format procurement mandates, plus anyone standardized on LibreOffice or Apache OpenOffice Impress. A DAM that ingests presentation assets from multiple departments or external partners should expect at least occasional .odp files and needs indexing and preview support for the format rather than treating it as a rare edge case.

Yes. ODP is a ZIP archive containing plain XML, and slide text, speaker notes, and structural data live in content.xml as openly published, human-readable markup. A DAM's indexing pipeline can unzip the file and parse content.xml directly with a standard XML library, pulling text for full-text search and metadata without ever launching LibreOffice Impress, OpenOffice, or PowerPoint. This makes ODP indexing comparatively lightweight next to formats that require a rendering engine to expose text.

Basic text, bullet layout, and images generally survive conversion well, but ODF and OOXML model animations, transitions, and master-slide formatting differently, so those elements can shift or drop entirely during conversion. Embedded fonts and linked (rather than embedded) media are additional risk points, since a link that resolved correctly in the ODF package may break after conversion. A DAM that auto-converts ODP to PPTX should keep the original .odp as the archival master and flag converted files for visual verification before distribution.

Yes, when a video is embedded rather than linked, it sits as a discrete file inside the ODP's ZIP archive, typically referenced from the Pictures or media folder listed in META-INF/manifest.xml. A DAM can unzip the package and pull the video out directly, without launching Impress, the same way it extracts embedded images. Linked videos, referenced by external path or URL instead of embedded, are the exception: the DAM only sees the reference and must resolve it separately.

Yes, notes are stored as part of each slide's XML structure in content.xml, and a DAM's indexer can include them in full-text search if configured to parse that section.

ODP has a strong case for archival use: it's a vendor-neutral format standardized by OASIS in 2005 and ratified as ISO/IEC 26300 in 2006, with an openly published XML schema that doesn't depend on any single vendor continuing to support it. That gives it preservation characteristics comparable to PPTX, which is itself an open ISO/IEC 29500 standard. As with any ZIP-based container, a DAM should still verify embedded (not linked) fonts and media to avoid dependency loss over time.

Yes, typically through the same rendering pipeline: a headless LibreOffice or OpenOffice instance opens the file server-side and exports each slide as an image, which works for ODP just as it does for PPTX and other OOXML formats. Because both are ZIP-based XML containers with a documented slide/page model, the same conversion service can usually handle both without format-specific logic, though fonts referenced but not embedded in the file can cause layout to shift in the rendered thumbnail.