Synology Surveillance Station Client explained for practical video monitoring

a[data-rs-seo-link]{text-decoration:underline!important;color:#1a56db!important;cursor:pointer!important;}a[data-rs-seo-link]{text-decoration:underline!important;color:#1a56db!important;cursor:pointer!important;}
What the Synology Surveillance Station Client does
Synology Surveillance Station Client is a desktop utility for accessing Surveillance Station on Synology NAS and NVR systems without relying entirely on a browser. In day-to-day monitoring, the main reason to install it is to improve multi-camera live view, reduce browser-related video format limits, and use functions such as Monitor Center, playback, and GPU-assisted decoding. It does not replace Surveillance Station itself. The recording server, camera settings, licenses, users, and storage policies remain on the Synology system. As of November 17, 2026, Synology’s public materials show Surveillance Station 9.3.0 as the current major server release and list Surveillance Station Client 2.2.3-2598 in the official utility archive.
That distinction is important because many setup problems start with treating the desktop client as the entire surveillance platform. The client is the operator interface. The NAS or NVR still records video, stores evidence, applies user privileges, and enforces camera licensing. For broader planning around NVRs, IP cameras, and monitoring layouts, see our surveillance systems coverage.

Where it fits compared with browser, mobile, and local display options
Synology provides several ways to operate Surveillance Station. Synology’s user guide describes the web interface as HTML5-based and plugin-free, with Google Chrome recommended for the best browser experience. The same guide positions the desktop client as the option designed to avoid browser limitations and improve performance when multiple surveillance applications are open.
| Access method | Best fit | Main limitation to check |
|---|---|---|
| Surveillance Station Client | Operator workstations, control rooms, regular playback review, multi-camera monitoring | Requires a supported desktop operating system and adequate local decoding performance |
| Web browser | Occasional administration, quick checks, systems where installing software is not practical | Codec and feature support can vary by browser and device |
| DS cam | Mobile alerts, quick live view, camera checks while away from the desk | Small-screen workflow is not ideal for extended evidence review |
| Local Display or VisualStation | Dedicated monitors, reception areas, and TV-wall style viewing | Hardware-specific deployment and feature differences |
In practice, the browser is useful when convenience is the priority. The desktop client is the better fit when monitoring quality, codec support, and workstation performance matter more. A security desk watching several cameras for hours should not be designed around the same access method as a manager doing a quick monthly review.
Compatibility and version checkpoints to verify
Before deploying Synology Surveillance Station Client across multiple PCs or Macs, check both the server package and the workstation utility. Synology’s current technical specifications list the client for Windows 10 and macOS 11 or above, and point to a Core i5 or above as a practical CPU reference for client-side monitoring. The current public utility archive lists version 2.2.3-2598 with a Windows x64 installer, a Windows x64 portable zip, a macOS x64 disk image, and a macOS arm64 disk image. It does not show a current Linux package in that version folder, so Linux-based monitoring desks should be validated before purchase or rollout.
| Date | Synology note | Why it matters for the client |
|---|---|---|
| September 26, 2024 | Surveillance Station 9.2.1 moved H.265 media processing from the server to end devices in many cases. | Workstation GPU, driver, and codec capability became more important for H.265 deployments. |
| November 26, 2024 | Surveillance Station 9.2.2 required Surveillance Station Client 2.1.3 or above. | Old desktop clients may fail or lose expected behavior after a server update. |
| February 5, 2026 | Surveillance Station 9.2.5 was identified as the last version to support DSM 6.2.4. | Sites still on older DSM versions need an upgrade plan before moving beyond that branch. |
| September 22, 2026 | Surveillance Station 9.3.0 required DSM 7.0-41890 or above and introduced server-side changes such as a redesigned desktop, built-in CMS, removed multicast streaming, and default recording rotation for new installations. | Client rollout should be coordinated with server release notes, especially for multi-site and multicast-dependent environments. |
These are not just release-note details. They can affect whether a camera wall remains smooth, whether H.265 streams display properly, and whether a workstation can still be used as expected after the NAS package is updated.
A practical setup checklist for monitoring workstations
A clean deployment starts with version alignment. Avoid downloading the utility from unofficial software mirrors, because surveillance workstations often have access to live feeds, recordings, exported evidence, and administrator sessions. Use Synology’s official distribution channels and keep a record of the client version installed on each workstation.
- Confirm the server version. Open Surveillance Station on the Synology system and verify the installed package version before changing the client.
- Read the relevant release notes. Pay special attention to compatibility, codec, CMS, recording, and security items.
- Install the matching desktop client. For current deployments, confirm whether the workstation needs Windows x64, macOS Intel, or macOS Apple silicon media.
- Sign in with a named user account. Avoid shared administrator logins. Use Surveillance Station privilege profiles to limit camera, playback, export, and management access.
- Test the real workflow. Verify live view, playback, timeline navigation, export, snapshots, audio if used, and any PTZ controls that operators need.
- Document the fallback path. If the desktop client fails during an incident, operators should know whether to use Chrome, DS cam, or another authorized workstation.
Do not treat a successful login as a completed deployment. A workstation can authenticate correctly and still perform poorly if it cannot decode the selected camera streams, if permissions are incomplete, or if the network path to the NAS is unstable.
Performance, codecs, and GPU acceleration
The most common reason to prefer Synology Surveillance Station Client is video handling. Synology’s technical specifications list supported surveillance video formats including MJPEG, H.264, H.264+, H.265, H.265+, MPEG4, and MxPEG, while also noting that support can vary by client device specifications. In practical terms, the camera stream, the NAS package version, the desktop client, the operating system, and the local GPU all matter.
GPU acceleration can reduce CPU load when the workstation supports the required decoding path. Synology’s GPU acceleration guidance has historically focused on hardware decoding support such as DirectX Video Acceleration 2.0 and H.264 or H.265 support on the client side. If live view stutters, shows blank video, or becomes delayed, troubleshoot in this order:
- Update the desktop client and the NAS Surveillance Station package to compatible versions.
- Update the graphics driver on the monitoring workstation.
- Test the same camera in H.264 if H.265 playback is unreliable on that machine.
- Use camera substreams for dense live-view layouts, then reserve full-resolution streams for playback or selected channels.
- Reduce layout density before assuming the NAS is the bottleneck; the viewing PC may be the limiting device.
This point is especially important after server releases that shift more media handling to end devices. The benefit is lower server-side workload, but the tradeoff is a stronger dependency on workstation hardware. See also: Access Control.
Security and operations considerations
Surveillance video is operationally sensitive. A desktop client that can view, export, or search recordings should be managed like other privileged security software. Synology’s own documentation highlights privilege profiles, playback permissions, watermarks, privacy masking, recording encryption, logs, and client management as part of the broader Surveillance Station environment. Use those controls deliberately rather than relying on workstation location as the only protection.
- Least privilege: Operators who only monitor live views should not automatically receive camera configuration or export rights.
- Named accounts: Use individual accounts so logs can identify who viewed, changed, or exported footage.
- Evidence handling: Test export permissions and watermark settings before an incident, not during one.
- Network exposure: Prefer VPN or controlled remote access paths over exposing NAS services directly to the internet.
- Update discipline: Treat client updates and server updates as one change window, especially in sites with H.265 cameras or CMS.
Installing Synology Surveillance Station Client on another workstation does not add a camera license requirement by itself. Device licenses apply to cameras and other surveillance devices connected to Surveillance Station, while the client is an access tool for authorized users.
Frequently asked questions
Do I need Synology Surveillance Station Client if the browser works?
Not always. A browser is fine for quick administration and occasional viewing. The desktop client makes more sense for regular monitoring, multi-camera layouts, H.265-heavy environments, and workstations where browser codec limitations or tab behavior create operational friction.
Is Surveillance Station Client the same as Surveillance Station?
No. Surveillance Station is the VMS package running on the Synology NAS or NVR. Surveillance Station Client is the desktop application used to access that system from a Windows or macOS workstation.
Does the client support every camera feature?
No client path should be assumed to support every feature equally. Synology notes that joystick support, fisheye dewarping, Smart Search, Live View Analytics, and codec behavior can vary by client type and device capability. Test the exact cameras and layouts you plan to use.
Why does H.265 video work on one computer but not another?
H.265 playback depends on the client device’s hardware decoding ability, operating system support, drivers, and Surveillance Station version. After Synology moved more H.265 processing to end devices in the 9.2.1 period, weaker or older workstations became more likely to show decoding problems.
Should I update to Surveillance Station 9.3.0 before installing the client?
Update planning should start with the NAS model, DSM version, camera formats, and site requirements. Surveillance Station 9.3.0 requires DSM 7.0-41890 or above and includes changes that can affect CMS, multicast streaming, recording rotation, and the server desktop. Test before applying it to a production monitoring environment.


