315 Extensions, No Conversion Step

Each format carries its MIME type, content-type classification, rendering engine and file signature.

Three rendering paths run underneath:

1. The native pipeline for video, audio and web-native images
2. ImageMagick for the long tail of raster formats, which is where most of the 187 image extensions live
3. A document engine for office, CAD, email and page-description formats

Video and audio are transcoded to streaming renditions on ingest. Images and documents are rendered for in-browser viewing without the originating application, so a CAD file or an obscure raster format is reviewable by someone who does not have the software that made it.

DICOM is handled as medical imaging rather than as a generic image, preserving study and series structure. It has its own page.

The accepted format list is managed per portal, alongside a separate restricted-extension blocklist that refuses types outright. A deployment that should never accept executables says so once.

• Body camera footage — legacy archives from decommissioned vendor systems
• CCTV and surveillance — proprietary camera output
• eDiscovery — mixed production sets nobody curated in advance

• Support means ingest, store and serve. Transcoding, in-browser preview and AI eligibility are stated on the capability that performs the operation, not inherited from this list.
• Upload types are governed per portal by the accepted list and the restricted-extension blocklist, so what a given deployment accepts may be narrower than what the platform supports.

• 315 distinct extensions across video, audio, image, document and miscellaneous types.
• 187 image formats, which is the figure that separates a real format list from a marketing one.
• Documents and images render in-browser without the originating application.
• Upload types are governed per portal by an accepted list and a restricted-extension blocklist.