VERIFRAME

Formats → Conversion engine

License Veriframe as your CCTV conversion engine

For systems integrators, evidence-platform vendors and primes: when a contract puts proprietary CCTV in scope, you need to convert and play any DVR export — without building the decoders yourself. That is what Veriframe is.

Why it comes up in a bid

Public bodies — forces, transport authorities, courts, local government — hold footage in formats only the manufacturer's own software will open. A response that cannot open, play and hand on that footage does not clear the evaluation, and reverse-engineering a dozen proprietary containers is not something you want on the critical path of a tender. It is common for several bidders to reach the same conclusion and all look for the same conversion capability behind their submissions.

What you can put behind your bid

Engagement is as light or close as the work needs: send exports and receive the deliverables, or talk to us about a tighter arrangement for a specific programme. See every format and what each conversion includes →

Formats covered

.xba, .hvv, .dav, .synav, .pdt / .idt, .XI1, .hbox, .sec, .avi, .SYN, .cve — plus standard containers passed through. Each was reverse-engineered from real exports and tested against real jobs; nobody else publishes this range. Full list →

What procurement will ask — answered

Bidding something with proprietary CCTV in scope? Tell us the recorders involved and the timetable. We will tell you what converts, provide a capability statement for your response, and look at a real sample at no charge.

Email enquiries@veriframe.co.uk

Questions integrators ask

Can I license Veriframe as the conversion engine behind my own bid or platform?

Yes — that is a large part of why it exists. When a contract puts proprietary CCTV in scope, the integrator bidding it needs a way to convert and play those formats without building the decoders. We provide that capability: send us the exports and receive standard MP4, a browser player and a verifiable certificate; or we discuss a closer arrangement. You do not have to reverse-engineer a single container.

Which proprietary CCTV formats does the engine convert?

The recorders and containers on our formats page — .xba, .hvv, .dav, .synav, .pdt / .idt, .XI1, .hbox, .sec, .avi, .SYN, .cve, and standard containers passed through — each worked out from real exports and tested against real jobs. If your bid names a recorder we do not yet list, send a sample: new formats are usually a matter of days, which is often faster than a tender timetable.

How does this fit a public-sector tender?

As a named technology capability behind your response. We can provide a capability statement covering the formats handled, the evidential certificate and its published verification method, and the security posture procurement will ask about — UK processing, ISO/IEC 27001-certified data centres, a published DPA, 24-hour deletion and no backups. We are glad to complete a security questionnaire.

Is the conversion defensible as evidence?

Every conversion carries a certificate that fixes the original file and the delivered video by their SHA-256 fingerprints, and — where the recording is standard video — shows it was copied rather than re-encoded. The verification method is published, so the other side can repeat it without our involvement. We do conversion and recovery only: no speed estimation, image comparison, enhancement or forensic interpretation. That boundary is deliberate and stated up front.

See it for yourself