Third-party camera integration
Reolink with Synology Surveillance Station
Reolink documents three practical connection paths for Surveillance Station: the Reolink protocol, ONVIF and RTSP. They are not interchangeable. For supported models, Reolink’s own guidance favors the Reolink protocol when AI events or PTZ functions matter, while ONVIF is a broad standards-based option and RTSP is a useful fallback for basic streaming. Dual-lens cameras such as TrackMix need special attention because channels and licenses can multiply.
Quick answer
Use the richest supported protocol your camera needs
Start with the exact Reolink model and Synology compatibility status. If you need camera AI events or PTZ, prefer the supported Reolink protocol where available; use ONVIF for standards-based integration and RTSP when the requirement is primarily a stable video stream. Enable only the required camera-side ports.
Live Amazon products
Hardware and licenses relevant to this surveillance decision
This Sprint 9G catalogue tracks the Synology NAS, DVA appliances, cameras, license packs and selected Reolink examples used by these pages. Surveillance hard-drive cards are read from Cloudzat Storage Price Intelligence in read-only mode. Product cards support planning but never override Synology's live compatibility list, NVR Selector, license rules or camera firmware requirements.
Technical decision
The connection method determines more than picture quality
Protocol choice affects discovery, events, PTZ, audio, stream selection and sometimes license/channel behavior. A camera that produces live video over RTSP may still be a poor Surveillance Station fit if the project depends on smart detections or dual-lens control.
Interactive surveillance tool
Reolink + Synology Setup Selector
Use this as a planning aid. It applies the inputs you provide, but final camera limits, compatibility, licensing, package behavior and cloud plan details must be checked against Synology's current documentation and the exact hardware/firmware in use.
Deployment checklist
Four checks before a surveillance rollout
Prove the camera path
Verify the exact model, firmware and protocol in Synology Camera Support before buying or rolling out a large fleet.
Calculate licenses
Count actual device channels, multi-lens streams and special devices, then subtract only the licenses included with the chosen recorder.
Size by bitrate
Use configured Mbps, recording hours and retention days. Resolution alone is not a reliable surveillance-storage number.
Test recovery
After setup or upgrade, verify new recordings, playback, notifications, remote access and the procedure for retrieving critical footage.
Start with Reolink and Synology support data
Reolink’s guide documents multiple connection methods while Synology’s list shows tested device support and available capabilities. Compare both vendors before choosing a protocol so an undocumented feature assumption does not drive the design.
Start with Reolink and Synology support data: Compare both vendors before choosing a protocol so an undocumented feature assumption does not drive the design. Reolink’s guide documents multiple connection methods while Synology’s list shows tested device support and available capabilities.
Enable the required ports on the camera
ONVIF, RTSP and vendor integration rely on camera services that may be disabled by default on some Reolink firmware. Enable only the protocol ports required for your selected method and document them for later troubleshooting.
Enable the required ports on the camera: Enable only the protocol ports required for your selected method and document them for later troubleshooting. ONVIF, RTSP and vendor integration rely on camera services that may be disabled by default on some Reolink firmware.
Use Reolink protocol for richer supported integration
Reolink recommends its protocol when AI detection and PTZ functionality are priorities on supported cameras. Select the exact model profile in Surveillance Station and test person/vehicle events plus PTZ before scaling.
Use Reolink protocol for richer supported integration: Select the exact model profile in Surveillance Station and test person/vehicle events plus PTZ before scaling. Reolink recommends its protocol when AI detection and PTZ functionality are priorities on supported cameras.
Use ONVIF for broad interoperability
ONVIF can be a strong option when a camera supports the relevant profile and native integration is unavailable or unnecessary. Verify the ONVIF port, credentials, stream and event behavior using the actual camera firmware.
Use ONVIF for broad interoperability: Verify the ONVIF port, credentials, stream and event behavior using the actual camera firmware. ONVIF can be a strong option when a camera supports the relevant profile and native integration is unavailable or unnecessary.
Use RTSP as the simple stream fallback
RTSP can deliver a stable camera feed when richer integration paths are problematic or not required. Accept that event, PTZ and configuration integration may be limited and keep advanced logic elsewhere if needed.
Use RTSP as the simple stream fallback: Accept that event, PTZ and configuration integration may be limited and keep advanced logic elsewhere if needed. RTSP can deliver a stable camera feed when richer integration paths are problematic or not required.
TrackMix needs channel planning
Dual-lens TrackMix models can expose multiple streams/channels, and Reolink documents integration details that affect how they appear in Surveillance Station. Decide whether both lenses must be recorded and calculate device licenses for the chosen method before purchase.
TrackMix needs channel planning: Decide whether both lenses must be recorded and calculate device licenses for the chosen method before purchase. Dual-lens TrackMix models can expose multiple streams/channels, and Reolink documents integration details that affect how they appear in Surveillance Station.
AI events should be tested end to end
A Reolink camera can detect people or vehicles locally while Surveillance Station fails to receive the event through an unsuitable protocol. Create a real test event and verify the rule, recording and notification in Surveillance Station.
AI events should be tested end to end: Create a real test event and verify the rule, recording and notification in Surveillance Station. A Reolink camera can detect people or vehicles locally while Surveillance Station fails to receive the event through an unsuitable protocol.
PTZ is more than moving the camera once
Presets, patrols and automatic tracking can depend on protocol support beyond basic pan/tilt commands. Test every PTZ function operators need, not only manual movement from one client.
PTZ is more than moving the camera once: Test every PTZ function operators need, not only manual movement from one client. Presets, patrols and automatic tracking can depend on protocol support beyond basic pan/tilt commands.
Keep bitrate and codec controlled
Reolink cameras can offer multiple resolutions and streams that change storage and client load significantly. Pick the recording stream deliberately, then use its configured bitrate in the retention calculator.
Keep bitrate and codec controlled: Pick the recording stream deliberately, then use its configured bitrate in the retention calculator. Reolink cameras can offer multiple resolutions and streams that change storage and client load significantly.
Separate camera credentials from admin credentials
Dedicated camera users reduce the blast radius if credentials are exposed in a VMS or troubleshooting workflow. Create least-privilege accounts where the camera firmware supports them and store credentials securely.
Separate camera credentials from admin credentials: Create least-privilege accounts where the camera firmware supports them and store credentials securely. Dedicated camera users reduce the blast radius if credentials are exposed in a VMS or troubleshooting workflow.
Firmware updates deserve a pilot camera
Camera updates can change ONVIF endpoints, event behavior or codec defaults even when the model name is unchanged. Update one noncritical unit, verify all Surveillance Station functions, then roll out fleet-wide.
Firmware updates deserve a pilot camera: Update one noncritical unit, verify all Surveillance Station functions, then roll out fleet-wide. Camera updates can change ONVIF endpoints, event behavior or codec defaults even when the model name is unchanged.
Document the protocol on every camera
Mixed deployments become difficult to troubleshoot when operators cannot tell whether a device uses Reolink protocol, ONVIF or RTSP. Record protocol, ports, stream, firmware and license channel count in the camera inventory.
Document the protocol on every camera: Record protocol, ports, stream, firmware and license channel count in the camera inventory. Mixed deployments become difficult to troubleshoot when operators cannot tell whether a device uses Reolink protocol, ONVIF or RTSP.
Questions people ask
Reolink and Synology questions
Can Reolink cameras work with Synology?
Yes. Reolink documents Synology integration using Reolink protocol, ONVIF and RTSP, with capabilities depending on the exact camera and method.
Which Reolink protocol should I use?
Use the richest supported option for your requirements; Reolink recommends its protocol for AI/PTZ use on supported models, with ONVIF and RTSP as alternatives.
Do I need to enable ONVIF on Reolink?
If you choose the ONVIF method, enable the relevant ONVIF service/port in the Reolink configuration before adding the camera.
Can I use RTSP only?
Yes for basic streaming in supported setups, but you may lose richer events, PTZ or camera-management features.
Will Reolink AI events work in Surveillance Station?
They can when the selected protocol/model integration exposes those events; test person/vehicle detections with the exact firmware.
Does Reolink PTZ work with Synology?
It can on supported integrations, but presets, patrols and tracking should be tested rather than inferred from basic pan/tilt.
Does TrackMix need two Synology licenses?
Dual-lens/channel behavior can require additional licensing depending on how streams are added, so follow current Reolink and Synology guidance for the selected method.
What causes Reolink connection failures?
Common causes include disabled protocol ports, wrong credentials, network segmentation, an incorrect camera profile or firmware/protocol mismatch.
Should I use H.265 with Reolink?
Use it when the camera, Synology system and viewing/export clients support the workflow; calculate storage from the actual configured bitrate.
Can I mix Reolink and Synology cameras?
Yes, but keep a per-camera record of protocol, firmware, license use and feature support because the integration behavior differs.
Official references and methodology
Verify the exact camera, recorder, package build and licensing state
This page follows Reolink’s official Synology integration guide and cross-checks licensing and camera support against Synology documentation. Cloudzat does not assume that a protocol supported by one firmware revision exposes identical AI, PTZ or multi-lens behavior on every model.
- Reolink Synology Surveillance Station setup guide
- Synology IP Camera Support List
- Synology Surveillance Device License Pack
- Synology Add Camera tutorial
As an Amazon Associate, Cloudzat may earn from qualifying purchases. Prices, camera firmware, product availability, license rules, Surveillance Station behavior and cloud-service plans can change. Verify the exact Synology model, camera support entry, package release notes and current service terms before purchasing hardware or changing a production surveillance system.