CCTV Main Stream vs Substream: Recording and Viewing Configuration
Essential Security Supplies
The main stream normally provides the higher-quality picture intended for recording or detailed review. A substream is a separately configured, usually lighter video feed that can make multi-camera live viewing and remote access more practical. Configure both deliberately: choosing the wrong stream for recording can permanently reduce available evidence detail.
Understand what each stream is doing
A camera can expose several profiles at different resolutions, frame rates, bitrates and compression formats. The names main stream and substream are conventional; exact behaviour depends on the camera and recorder. Some systems record the main stream and switch automatically to a lower stream for multiple live tiles, while others let the operator select. Verify the selected profile for each recording, desktop layout, mobile view and event snapshot.
Configure evidence recording first

Begin with the scene's identification requirement, pixel density, movement speed and retention target. Set a suitable main-stream resolution, frame rate, codec, bitrate controls and recording schedule. Check a downloaded playback clip, not merely the live preview. If a recording menu unexpectedly selects the substream, correct it and retest an actual new recording. Do not assume that changing live-view quality also changes the stored video.
Set a useful substream without hiding incidents
For a dense 16-camera overview, a lighter substream can reduce client decoding load and unnecessary wide-area traffic. However, a low-resolution tile may be poor for recognising small objects. Operators should have a reliable way to open the corresponding main stream for investigation. Confirm that event pop-ups, digital zoom, snapshots and third-party integrations display the intended profile. A broken substream may show a blank tile even while the main recording is healthy.
Bandwidth and remote viewing

Each active stream consumes bandwidth when transmitted, and multiple clients can add demand depending on the architecture. An internet connection is not required for local recording, but remote live viewing uses the available uplink or a relay service. Calculate with measured per-stream rates and concurrent viewers, not simply the number of installed cameras. Check whether mobile apps automatically adapt quality and whether they permit a manual switch that can saturate a limited link.
Commission and document each viewing path
In the camera interface, verify both profiles remain enabled after saving and rebooting. On the recorder, identify the recording profile and the default multi-view profile. On the VMS workstation, open one camera full-screen and many cameras simultaneously, checking CPU use, dropped frames and switching delay. Repeat remotely using the intended device where authorised. Document resolution, frame rate, codec, target bitrate, stream URL/profile and responsible operator.
Network, compatibility and safety checks

Before making changes, confirm that the camera, recorder and VMS all support the intended setting at the installed firmware revisions. Save the original configuration and identify a recovery route. Do not assume equivalent terminology across manufacturers. Coordinate any recording interruption with the authorised site contact, because changing profiles can temporarily affect monitoring, event processing or retention. Record the operator, date, camera location and affected services in the commissioning report.
A practical sign-off checklist
Capture a baseline image and video clip. Note the selected stream, resolution, frame rate, codec, bitrate mode, illumination and relevant lens or exposure settings. Apply one controlled change at a time, then record a fresh clip of a suitable moving subject. Review the clip locally and remotely where authorised, and use the actual evidence export process. Confirm date and time, playback continuity, image usability and the ability to restore the prior state. Keep the final settings in the as-built documentation.
Common mistakes to avoid
Do not judge the result only from a phone screen or low-resolution monitoring tile. Do not conclude that one manufacturer's default is correct for a different camera or scene. Avoid changing compression, resolution, exposure and lens settings simultaneously, because that hides which adjustment helped. A clean daytime picture does not prove night-time performance. Where the requirement is identification or evidential playback, test that task directly rather than relying on a manufacturer's headline resolution specification.
When to seek a second camera or design change
Some problems cannot be corrected by a menu setting. If required targets occupy very different distances, move rapidly through dim lighting or fall outside the useful field of view, a different camera position, dedicated identification view or suitable illumination may be needed. Validate mounting positions, cables, PoE supply and storage capacity before making design recommendations. The correct outcome may be a documented limitation and revised specification, not an overstated claim that a single adjustment covers every operating condition.
Example: a busy operator viewing sixteen cameras
Suppose an operator station shows sixteen small tiles and opens one full-screen feed during an incident. Configure the grid to use appropriate substreams if the platform supports it; reserve the main stream for evidence recording and detailed review. Test the exact transition from overview to full screen and back, including a second operator connecting at the same time. Capture the client's CPU utilisation and any warning of exceeded decoder resources. Then export a stored incident clip and inspect whether the recorded file really contains main-stream resolution and timestamps. This example is a design method rather than a universal bandwidth specification. If the grid is clear but exports are unexpectedly low resolution, investigate the recorder's recording profile rather than increasing every client's live-view setting. If the grid freezes while recordings remain sound, investigate substream negotiation, network paths and workstation load separately. Document which profile each client layout uses.
Frequently asked questions
Should CCTV always record the main stream?
Usually the higher-quality stream is preferred for evidence, but verify it against retention, scene needs and system capabilities.
Does a substream create another recording?
Not necessarily. It may be used only for live display; inspect the recording settings and recorded files.
Why is a multi-camera grid blurry?
It may be showing substreams to conserve decoding resources. Open a full-screen view and test the stored recording.
Can disabling substreams improve performance?
Often not. They can reduce display and network load. Diagnose which stream is actually failing before changing profiles.
Next step for NZ installers
For a project-specific CCTV design, confirm the equipment, site conditions and recording objectives before requesting a technical specification or trade enquiry from Essential Security Supplies. This draft requires genuine product imagery and verified internal destinations before it can be considered for publication.
Need Advice on Security Equipment?
Discuss product suitability, specifications and project requirements with Essential Security Supplies.