ONVIF Profile G acceptance testing for edge recording and retrieval

Profile G standardizes important recording and retrieval interfaces, but a resilient edge-recording design still needs capacity, outage, recovery, and evidence tests.

Executive summary

What you need to know

Profile G standardizes important recording and retrieval interfaces, but a resilient edge-recording design still needs capacity, outage, recovery, and evidence tests.

Potentially affected

Video systems using camera or encoder storage, recording-capable devices, NVRs, VMS clients, or edge recording as a primary recorder or network-outage safeguard.

DSE recommendation

Verify exact Profile G conformance and run controlled storage, outage, retrieval, and reintegration tests against the real camera, media, and VMS combination.

What Profile G covers

Source fact: ONVIF Profile G is designed for IP-based video storage and retrieval. A conformant device, such as a network camera or encoder, can record video over the network or on the device itself. A conformant client, such as VMS software, can configure, request, and control recording from a Profile G device.

ONVIF’s 2014 release announcement describes a broader recording workflow that includes on-board storage, search, retrieval, and media playback. The current profile page also identifies receipt of audio and metadata streams when the client supports those features. That conditional wording is important: a Profile G label alone does not establish that every client accepts audio or metadata.

Profile G provides standardized interfaces, not a storage-service guarantee. It does not assign an SD-card endurance rating, calculate retention, promise uninterrupted capture for every outage, validate timestamps, or certify that a VMS will reconcile every edge recording after connectivity returns. Those outcomes depend on the exact device, media, client, configuration, clock source, network behavior, and supported features.

Define the recovery use case

First decide why edge storage exists. It may be the primary recording destination, a short network-failure buffer, or a secondary evidence source. Define the expected recording mode, event triggers, frame rate, bitrate, audio and metadata needs, retention target, and maximum anticipated outage. Use manufacturer endurance and compatibility information for the actual media rather than deriving capacity from Profile G.

Conformance must be checked for both sides of the intended workflow and for their exact installed versions. A feature list should be reviewed before testing so a conditional function is not mistaken for a universal requirement.

DSE acceptance checklist

DSE recommendation: This checklist is DSE operational synthesis; ONVIF does not prescribe this site-test sequence.

  1. Verify the exact device and client versions in ONVIF’s registry and retain their feature documents.
  2. Confirm supported media, health monitoring, usable capacity, overwrite behavior, and time synchronization from current manufacturer guidance.
  3. Create known recordings and prove search, retrieval, playback, timestamps, and export from the client.
  4. Where required, confirm that audio and metadata survive the complete recording and retrieval path.
  5. Simulate an approved network interruption, keep it within the designed duration, and document device behavior.
  6. Restore connectivity and verify discovery, backlog availability, chronology, duplicates, gaps, and VMS reconciliation.
  7. Test full, removed, failed, or replaced media using safe procedures supported by the manufacturer.
  8. Record the tested limits and schedule periodic health and retrieval checks.

Official references

Primary reference

Review the official source

ONVIF — Profile G · Verified July 19, 2026

Open official reference ↗
Plan the next step

Need help applying this guidance safely?

DSE can help confirm applicability, protect service continuity, and validate the result across physical security and IT systems.

Talk with DSE