Synology setup workflow
Synology Surveillance Station Setup Guide
A clean Surveillance Station setup is easier when the NAS, camera network, storage pool, licenses and retention policy are prepared before the Add Camera wizard. Synology’s wizard can discover cameras and test connections, but those steps do not automatically validate storage sizing, event logic, permissions, backup or remote-access security. This guide turns setup into a repeatable checklist rather than a one-time click sequence.
Quick answer
Prepare the camera and recording policy before Add Camera
Give the camera a stable network identity, update its firmware, verify it appears on Synology’s compatibility list or through a supported ONVIF path, and know the intended codec, frame rate, bitrate and retention policy before adding it. Then test recording and playback after the wizard finishes.
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
A successful Test Connection is only the beginning
The Add Camera wizard confirms connectivity and allows stream settings, but a production setup must also prove scheduled recording, event recording, retention rotation, alerts, permissions, remote viewing and recovery. Configure one representative camera fully before cloning settings across the fleet.
Interactive surveillance tool
Surveillance Station Setup Checklist
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.
Prepare DSM and Surveillance Station
A supported DSM build, healthy storage pool and current Surveillance Station package provide the base before any camera is added. Resolve storage warnings and package updates before camera onboarding so setup errors are not mixed with platform problems.
Prepare DSM and Surveillance Station: Resolve storage warnings and package updates before camera onboarding so setup errors are not mixed with platform problems. A supported DSM build, healthy storage pool and current Surveillance Station package provide the base before any camera is added.
Give cameras stable network addresses
Cameras that repeatedly change IP addresses create avoidable reconnection and troubleshooting work. Use a documented static address or DHCP reservation and keep camera addressing on a predictable network segment.
Give cameras stable network addresses: Use a documented static address or DHCP reservation and keep camera addressing on a predictable network segment. Cameras that repeatedly change IP addresses create avoidable reconnection and troubleshooting work.
Confirm exact camera compatibility
Native support can expose more camera-specific functions than a generic protocol path, while ONVIF and RTSP remain useful fallbacks. Check the exact model and firmware in Synology’s support list before assuming PTZ, audio or smart events are available.
Confirm exact camera compatibility: Check the exact model and firmware in Synology’s support list before assuming PTZ, audio or smart events are available. Native support can expose more camera-specific functions than a generic protocol path, while ONVIF and RTSP remain useful fallbacks.
Choose Quick or Complete Setup deliberately
Synology’s Add Camera workflow offers faster and more detailed setup paths depending on how much stream configuration must be controlled. Use complete configuration when codec, bitrate, audio, retention or multi-stream behavior matters to the deployment.
Choose Quick or Complete Setup deliberately: Use complete configuration when codec, bitrate, audio, retention or multi-stream behavior matters to the deployment. Synology’s Add Camera workflow offers faster and more detailed setup paths depending on how much stream configuration must be controlled.
Use Test Connection before saving
The wizard can test camera IP, port, credentials and selected model/protocol before finalizing the device. Treat a failed test as a camera/network/protocol issue first instead of immediately changing storage or NAS settings.
Use Test Connection before saving: Treat a failed test as a camera/network/protocol issue first instead of immediately changing storage or NAS settings. The wizard can test camera IP, port, credentials and selected model/protocol before finalizing the device.
Set codec, FPS and bitrate intentionally
Video format, resolution, frame rate and bitrate determine bandwidth and retention, so defaults can silently oversize or undersize storage. Select the stream profile required for identification and analytics, then recalculate storage using the configured bitrate.
Set codec, FPS and bitrate intentionally: Select the stream profile required for identification and analytics, then recalculate storage using the configured bitrate. Video format, resolution, frame rate and bitrate determine bandwidth and retention, so defaults can silently oversize or undersize storage.
Build recording schedules around purpose
Continuous recording, motion/event windows and off-hours schedules each create different storage and evidence characteristics. Decide when continuous evidence is required and where event-only recording is acceptable instead of choosing one schedule for every camera.
Build recording schedules around purpose: Decide when continuous evidence is required and where event-only recording is acceptable instead of choosing one schedule for every camera. Continuous recording, motion/event windows and off-hours schedules each create different storage and evidence characteristics.
Set archive size and retention together
A recording volume can rotate footage by retention or storage thresholds depending on configuration. Document the intended number of days and confirm old footage disappears when expected without consuming the entire volume.
Set archive size and retention together: Document the intended number of days and confirm old footage disappears when expected without consuming the entire volume. A recording volume can rotate footage by retention or storage thresholds depending on configuration.
Create least-privilege viewer roles
Not every operator needs camera configuration, export or system administration rights. Separate viewers, investigators and administrators so normal monitoring credentials cannot casually alter the recorder.
Create least-privilege viewer roles: Separate viewers, investigators and administrators so normal monitoring credentials cannot casually alter the recorder. Not every operator needs camera configuration, export or system administration rights.
Test alerts with real events
Motion or analytics rules can look correct in the interface but fail because of camera-side zones, notification paths or permission settings. Walk through a representative event and verify detection, recording bookmark and notification delivery end to end.
Test alerts with real events: Walk through a representative event and verify detection, recording bookmark and notification delivery end to end. Motion or analytics rules can look correct in the interface but fail because of camera-side zones, notification paths or permission settings.
Prove remote access securely
Remote camera access should use supported secure paths and strong authentication rather than broadly exposing management interfaces. Test remote live view and playback from outside the LAN only after the local recording workflow is stable.
Prove remote access securely: Test remote live view and playback from outside the LAN only after the local recording workflow is stable. Remote camera access should use supported secure paths and strong authentication rather than broadly exposing management interfaces.
Document one camera as the template
A repeatable configuration record makes later replacements and expansions dramatically easier. Record firmware, IP, protocol, stream profile, retention, alert rules and license usage before onboarding the next camera model.
Document one camera as the template: Record firmware, IP, protocol, stream profile, retention, alert rules and license usage before onboarding the next camera model. A repeatable configuration record makes later replacements and expansions dramatically easier.
Questions people ask
Surveillance Station setup questions
How do I add a camera to Surveillance Station?
Use the Add Camera wizard, search or enter the camera address, choose the model/protocol, enter credentials, test the connection and then configure stream and recording settings.
Should cameras use static IP addresses?
A stable address or DHCP reservation is strongly preferable because it makes reconnection, documentation and troubleshooting predictable.
What is Quick Setup?
It is the faster onboarding path; use more complete configuration when you need deliberate stream, bitrate, audio, recording or retention settings.
Why does Test Connection fail?
Common causes include wrong IP/port/credentials, disabled ONVIF or vendor protocol, network segmentation, firewall rules or selecting the wrong camera model.
Should I use H.264 or H.265?
Choose a codec supported by the camera, NAS and viewing clients; H.265 can reduce bandwidth/storage at comparable quality but compatibility requirements still matter.
How do I set retention days?
Set the recording policy and archive/rotation rules, then verify that real recordings are retained and deleted according to the intended window.
Can I copy settings to many cameras?
Yes, but prove a representative camera model first so a bad stream or event configuration is not duplicated across the fleet.
Do I need licenses before adding cameras?
The system must have sufficient available Surveillance Device Licenses for the channels/devices being added.
What should I test after adding a camera?
Verify live view, recording, playback, event alerts, audio/PTZ where applicable and remote viewing.
Should I expose Surveillance Station directly to the internet?
Prefer supported secure remote-access methods, strong authentication and tightly scoped access rather than broad direct exposure.
Official references and methodology
Verify the exact camera, recorder, package build and licensing state
This guide follows Synology’s Add Camera workflow and supplements it with planning checks for stable addressing, bitrate, retention, licenses and recovery. Exact menu names and supported camera features can change with Surveillance Station, camera firmware and DSM versions.
- Synology Add Camera tutorial
- Synology IP Camera Support List
- Synology Surveillance Station specifications
- Synology Surveillance Device License Pack
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.