Source fact: Axis developer documentation explains that signed video adds cryptographic signatures to captured H.264 or H.265 video as Supplemental Enhancement Information, or SEI, within the codec stream. Information derived from frames is signed with a private key, and verification uses the corresponding public information carried with the signed data.
\nAxis ties signing to the camera’s unique identity through Axis Edge Vault. Its documentation describes the result as a way to determine whether footage has been altered after leaving the camera and to trace the footage to its originating device. Support is currently associated with devices that include Axis Edge Vault, and Axis provides product and API methods for checking whether the function exists.
\nThe recording path matters. Axis states that the SEI frames must be preserved during both recording and export. If a VMS, transcoder, exporter, or container conversion discards them, later verification cannot use the signed-video data. Axis File Player supports H.264 and H.265 in ASF and MKV and H.264 in MP4 for the documented verification workflow.
\n\nAxis product documentation distinguishes integrity verification from chain of custody. Signed video does not by itself prove who controlled the exported file, who viewed or copied it, whether collection was lawful, whether the camera clock and location were correct, or whether the scene outside the field of view contradicts the recording. Those questions require separate governance and evidence records.
\nSupport and default enablement can vary by device, AXIS OS release, content destination, VMS, export format, and configuration. Current product documentation must be used for the deployed model rather than assuming one behavior across the estate.
\n\nDSE recommendation: This is DSE operational synthesis, not a legal conclusion about admissibility or authenticity.
\n