Some Tuya cameras can connect to an NVR through ONVIF. But using Tuya Smart or Smart Life does not prove that the exact camera exposes ONVIF, and an ONVIF listing does not prove every NVR function has been tested.
For a real project, verify three layers separately:
1. the exact camera SKU and firmware list or expose ONVIF;
2. the NVR can discover and receive the required stream;
3. recording, playback, audio, PTZ, events and reconnect behavior work on the exact camera/NVR combination.

Real QZT C23B product photograph. Its current product page lists Tuya Smart and ONVIF; the photograph itself is not an NVR compatibility test.
Tuya is an ecosystem, not an ONVIF guarantee
A camera can use Tuya Smart or Smart Life and still have no ONVIF interface. The app ecosystem and the local video protocol are separate capabilities.

Real QZT C45L product photograph. Its current product page lists Tuya Smart / Smart Life and explicitly says no ONVIF, making it a useful counterexample to the idea that every Tuya camera supports ONVIF.
QZT already has a clear current example. The C45L product page lists Tuya Smart und Smart Life, while its platform section says no ONVIF.
That is the safest mental model:
> Tuya tells you which smart-device ecosystem the camera uses. It does not, by itself, tell you which local NVR protocols are enabled.
The reverse shortcut is risky too. If a product page lists ONVIF, that is a specification statement. It still does not tell you whether your recorder supports the same authentication, stream, codec, PTZ or event behavior.
What current QZT product pages actually say
Several current QZT standard IP-camera pages list both a Tuya-family app and ONVIF. These are useful starting points for an NVR sample test, not completed interoperability certifications.

Real QZT C12 product photograph. The table below reports current public specification wording, not a completed NVR test.
| QZT SKU | App listed on current page | ONVIF on current page | Video encoding listed | NVR function test status |
|---|---|---|---|---|
| C12 | Tuya Smart / Smart Life | Listed | H.264 | Not tested |
| C23B | Tuya Smart | Listed | H.264 | Not tested |
| C26 | Tuya Smart / Smart Life | Listed | H.264 | Not tested |
| C40 | Tuya Smart / Smart Life | Listed | H.264 | Not tested |
| C45L | Tuya Smart / Smart Life | No ONVIF listed explicitly | Check exact build | N/A for ONVIF unless a different documented build is supplied |
The important wording is listed, nicht verified with every NVR.
The C12 page tells buyers to check recorder compatibility on the sample if ONVIF matters. The C23B page goes further and tells buyers to test live view, recording and any needed controls on the actual NVR and approved sample. C26 and C40 similarly call for recorder behavior to be checked during installation or sample testing.
That is the right boundary for this article as well. The public specification is evidence that ONVIF is intended for those listed builds. It is not evidence that every cell in an integration matrix has passed.
What Tuya’s ONVIF implementation requires
Tuya’s own TuyaOS ONVIF documentation describes the IPC camera as the ONVIF server and the NVR as the client on the same LAN.

Real QZT C26 product photograph. Tuya’s platform documentation explains the protocol requirements; this image does not prove a particular NVR result.
The TuyaOS topic also makes several implementation details explicit:
– ONVIF has to be enabled in the camera solution;
– the IPC SDK must support RTSP for the client to receive the video stream;
– the ONVIF server uses HTTP Digest authentication for security;
– client authentication differences can cause connection or streaming failures;
– ONVIF and RTSP connection limits can be reached;
– the documented implementation includes ONVIF device, media and PTZ functions;
– event image capture is marked as not currently supported in that TuyaOS topic.
Those points explain why two products can both say “ONVIF” and still behave differently with the same NVR.
Do not copy a port, RTSP path, username or password from another Tuya-branded product. Use the settings documented by the exact camera build or generated by its authorized configuration flow.
A current third-party example shows what a supported implementation can look like. Nivian’s July 20, 2026 support article tells users to enable ONVIF in a Tuya Smart camera, set a password and then add the camera to the NVR. That is useful as an implementation example, but it is nicht a menu, credential or port template for QZT hardware.
ONVIF support is not the same as official ONVIF conformance
There is an important difference between saying a product exposes an ONVIF interface and claiming it is officially ONVIF conformant.

Pexels photograph of a surveillance control room. Formal ONVIF conformance is established by the ONVIF process and database, not by the appearance of an NVR setup.
ONVIF states that its Conformant Products database is the authoritative source for official conformance. It also says conformance is tied to the specific firmware/software version listed for that product.
Its Conformance Process requires the applicable profile support, test tools and submitted conformance documents before a product can claim official conformance.
So keep two fields separate:
| Question | Evidence |
|---|---|
| Does this QZT build list or expose ONVIF for a project? | Current model documentation + sample/integration test |
| Is the product officially ONVIF conformant? | Matching product and firmware/software entry in the ONVIF Conformant Products database |
This article does not claim official ONVIF conformance for any QZT model. If a project specification requires formal conformance, verify the exact supplied version in the ONVIF database before quoting it that way.
Test the integration as a versioned matrix
Finding the camera in the NVR is only the first test. A useful compatibility record separates every function the project depends on.

Real QZT C40 product photograph. Its current page lists ONVIF; actual NVR behavior remains a sample-test item.
Start with a sample on an authorized local network and record:
| Field | Result |
|---|---|
| QZT SKU | Exact ordered SKU |
| Hardware revision | Record from sample |
| Firmware version | Record exact version |
| App / project version | Record if relevant |
| ONVIF option visible | Yes / No / Not tested |
| RTSP stream | Yes / No / Not tested |
| Authentication method | Documented method only |
| Video preview | Pass / Fail / Not tested |
| Codec / resolution received | Record observed value |
| Audio | Pass / Fail / Not tested |
| NVR recording | Pass / Fail / Not tested |
| NVR playback | Pass / Fail / Not tested |
| PTZ | Pass / Fail / N/A / Not tested |
| Motion / event metadata | Pass / Fail / Not tested |
| Reconnect after camera reboot | Pass / Fail / Not tested |
| Reconnect after router / DHCP change | Pass / Fail / Not tested |
| NVR model + firmware | Exact version |
| Test date | YYYY-MM-DD |
| Evidence | Screenshot / log / recording ID |
Do not fill an untested cell with “Yes” because discovery or live video passed.
The same rule applies after a firmware change. A result recorded for one camera/NVR version pair should not silently become a permanent compatibility promise for every future build.
What to send a supplier before you order
A reproducible requirement is more useful than asking, “Does this Tuya camera support ONVIF?”

Real QZT C23B package image. Confirm the exact hardware and firmware supplied for the sample before using a compatibility result for a larger order.
Send the supplier this information before the sample is approved:
> We need the exact camera SKU for use on an authorized local network with [NVR model and firmware]. Please confirm the hardware and firmware version, whether this build exposes ONVIF and/or RTSP, the documented authentication method, supported stream codec/resolution, and whether video, audio, NVR recording/playback, PTZ and motion/event metadata have been tested. Please identify any functions that are not supported.
For a QZT project, also include:
– destination market;
– exact resolution/version required;
– whether Tuya Smart / Smart Life must continue working while the NVR records;
– whether audio is required through the NVR path;
– whether PTZ control is required from the NVR;
– whether motion/event metadata is required or only continuous video;
– what should happen after camera, router or NVR restart.
That gives engineering a test target instead of a vague “Tuya + NVR” promise.
Häufig gestellte Fragen
Do all Tuya cameras support ONVIF?
No. QZT’s current C45L page is a direct example: it lists Tuya Smart / Smart Life and explicitly says no ONVIF. Tuya’s own developer documentation also treats ONVIF as a capability that must be enabled in the IPC solution.
Which current QZT Tuya cameras list ONVIF?
As of September 18, 2026, the current QZT product pages for C12, C23B, C26 and C40 list a Tuya-family app and ONVIF. Treat that as a public specification listing. NVR live view, recording, playback, audio, PTZ, events and recovery still need the exact camera/NVR test.
If an NVR finds the camera, is the integration complete?
No. Discovery only confirms one part of the connection. Test the stream, codec/resolution, recording, playback, audio, PTZ if needed, events if needed and recovery after reboot.
Is “supports ONVIF” the same as “ONVIF conformant”?
No. Official conformance must match the product and firmware/software version in ONVIF’s Conformant Products database.
Should I use a default RTSP URL or password I find online?
No. Use only the settings documented for the exact camera and firmware or generated through its authorized configuration process. Different Tuya-based products can use different implementations.
Can the Tuya app and NVR work at the same time?
They may, but connection limits and implementation details can matter. Tuya’s documentation notes that the maximum number of ONVIF/RTSP connections can be reached. Test the exact mix of app viewing and NVR recording required by the project.
Die praktische Regel ist einfach: use the current specification to choose a sample, then use the exact camera, firmware and NVR to create the compatibility claim. “Tuya” is an ecosystem label. “ONVIF listed” is a specification. A completed compatibility matrix is evidence.