Hikvision cameras are the most widely deployed IP cameras in the world. Out of the box, Hikvision pushes users toward Hik-Connect — their proprietary P2P cloud platform — as the default remote viewing solution. You create a Hikvision account, add your device, and video streams through Hikvision's servers.
Many users — particularly those in security-sensitive environments, professional installers, and developers integrating camera feeds into applications — look for alternatives. There are good technical and privacy reasons to want your video stream to travel through infrastructure you control, rather than through servers operated by a Chinese state-linked manufacturer.
This guide covers the three practical alternatives: cloud relay, VPN, and port forwarding — with honest assessments of each, the complete Hikvision RTSP URL format, and step-by-step setup for TheRelay as the recommended solution.
Contents
What Is Hik-Connect and Why People Avoid It
Hik-Connect is Hikvision's cloud-based remote access platform. It works via a P2P (peer-to-peer) protocol — your NVR or camera registers with Hikvision's cloud, and when you open the Hik-Connect app remotely, the app connects to Hikvision's servers to locate your device and establish a video stream.
From a pure functionality standpoint, Hik-Connect works. The reasons security professionals and integrators avoid it fall into several categories:
Video Routes Through Hikvision Servers
Depending on your network conditions and the P2P negotiation, your video stream may route through Hikvision's relay servers rather than directly between your camera and your viewing device. This means Hikvision infrastructure has access to your video feed. For commercial CCTV systems, retail environments, critical infrastructure, or any deployment with privacy requirements, routing video through a third-party vendor's cloud is problematic.
Hikvision's Ownership and Regulatory Status
Hikvision is majority owned by CETC — a Chinese state-owned enterprise. In the United States, the FCC added Hikvision to its Covered List in 2022, restricting the use of Hikvision equipment in certain federal contexts. Multiple government agencies in the UK, Australia, and EU have issued advisories or restrictions on Hikvision equipment in sensitive locations. While using Hik-Connect on a commercial premises is not illegal, routing your surveillance footage through servers under the operational control of a state-linked entity is a risk posture that many organizations are not willing to accept.
Account Dependency and App Lock-In
Hik-Connect requires a Hikvision account, the Hik-Connect mobile app, and continued compatibility between your firmware version and the cloud platform. If Hikvision's servers are down, if they discontinue the service, or if your firmware becomes incompatible, remote access breaks. Developers building applications that consume camera streams cannot easily integrate Hik-Connect into custom pipelines.
RTSP Is Already Available
Every Hikvision camera and NVR supports standard RTSP streaming regardless of whether Hik-Connect is configured. The stream is there — you just need a way to access it remotely without using Hikvision's cloud. The alternatives below all use this standard RTSP capability.
Hikvision RTSP URL Formats
Before setting up any remote access method, you need your camera's RTSP URL. Hikvision uses a consistent URL structure across nearly all of their cameras and NVR channels.
Standard IP Camera (IPC) — Direct Connection
# Main stream (full resolution, highest bitrate)
rtsp://username:password@camera-ip:554/Streaming/Channels/101
# Sub stream (lower resolution, lower bandwidth — better for remote viewing)
rtsp://username:password@camera-ip:554/Streaming/Channels/102
# Third stream (if supported by the camera model)
rtsp://username:password@camera-ip:554/Streaming/Channels/103
NVR Channel Access
When cameras are connected to a Hikvision NVR, you access streams through the NVR's IP. Channel numbers correspond to the NVR's camera inputs:
# NVR channel 1, main stream
rtsp://admin:password@nvr-ip:554/Streaming/Channels/101
# NVR channel 2, main stream
rtsp://admin:password@nvr-ip:554/Streaming/Channels/201
# NVR channel 1, sub stream
rtsp://admin:password@nvr-ip:554/Streaming/Channels/102
# NVR channel 3, sub stream
rtsp://admin:password@nvr-ip:554/Streaming/Channels/302
The pattern: the first digit(s) of the channel number are the NVR input number, and the last two digits are 01 for main stream or 02 for sub stream.
Finding Your Camera's IP Address
If you don't know your camera's local IP address, use the Hikvision SADP Tool (free download from Hikvision's website) to scan your local network — it will discover and display all Hikvision devices on the LAN, including their IP addresses and firmware versions. Alternatively, check your router's DHCP client list for a hostname containing "Hikvision" or "HikVision".
Before setting up remote access, verify the RTSP URL works on your local network using VLC: open Network Stream and paste the URL above. If VLC shows the camera feed locally, the URL is correct and you're ready to set up remote access.
Alternative 1: Cloud Relay — Recommended
A cloud relay agent runs on a machine on your LAN, reads the RTSP stream from your Hikvision camera locally, and tunnels it to a cloud endpoint via an outbound-only encrypted connection. You access the camera through that cloud endpoint. Your video does not touch Hikvision's infrastructure at any point.
Pros
- No Hikvision account or Hik-Connect required
- Video routes through infrastructure you choose
- No port forwarding — outbound only
- Works behind CGNAT and corporate firewalls
- Stable cloud endpoint — no dynamic IP issues
- Token-based access control
- Multiple protocols: WebRTC, RTSP, HLS, RTMP, SRT
- Works with VLC, ffmpeg, OpenCV, any RTSP client
Cons
- Monthly cost ($2/stream/month)
- Requires agent machine on LAN
- Streams route through cloud (minimal added latency)
Step-by-Step: Hikvision via TheRelay
The complete setup takes under 5 minutes:
1 Create a TheRelay account at app.therelay.net.
2 Install the TheRelay agent on any macOS, Windows or Linux machine on the same LAN as your Hikvision cameras. The agent needs outbound internet access but no inbound ports.
3 Add your Hikvision camera in the dashboard. Paste the RTSP URL using the format above:
# Single Hikvision IPC — main stream
rtsp://admin:yourpassword@192.168.1.64:554/Streaming/Channels/101
# Hikvision NVR — channel 2 sub stream
rtsp://admin:yourpassword@192.168.1.10:554/Streaming/Channels/202
4 Generate an access token in the dashboard. Tokens can be scoped per camera or per account, and revoked at any time.
5 Access from anywhere using the cloud endpoint. TheRelay supports multiple protocols from the same stream source:
# RTSP endpoint (VLC, ffmpeg, OpenCV, any RTSP player)
rtsp://stream.therelay.net:554/live/{camera-id}?token={token}
# HLS endpoint (browser, mobile players)
https://stream.therelay.net/hls/{camera-id}/index.m3u8?token={token}
# SRT endpoint (broadcast tools, OBS)
srt://stream.therelay.net:9999?streamid={camera-id}&token={token}
# WebRTC (browser — sub-second latency)
# Accessible via the TheRelay dashboard or embedded player
Use any of these endpoints in VLC, ffmpeg, OpenCV, a custom application, or a browser. No Hikvision account, no Hik-Connect app, no Hikvision server involvement.
Best for: Professional installers, developers building integrations, anyone with privacy requirements, or deployments that need a stable endpoint independent of the camera's firmware or manufacturer's cloud status.
Alternative 2: VPN
A VPN connects your remote device to your local network as if it were physically present on the LAN. Once connected, you can reach the Hikvision camera directly using its local IP address — no third-party cloud involved.
Pros
- No cloud service between you and the camera
- Direct access to camera web interface
- No port forwarding of RTSP (VPN handles the tunnel)
- Works with any Hikvision software on the VPN client
Cons
- VPN server needed (router must support it, or separate device)
- Must install VPN client on every access device
- Does not work behind CGNAT without additional setup
- Cannot share camera access with third parties easily
- Complex configuration, especially for multi-site setups
WireGuard Setup (Recommended VPN Option)
Many modern routers (pfSense, OPNsense, Mikrotik, Ubiquiti) support WireGuard directly. If yours does not, you can run a WireGuard server on a Raspberry Pi or any Linux machine on the LAN.
# Install WireGuard on your LAN server (Ubuntu/Debian)
apt install wireguard
# Generate key pair
wg genkey | tee server-private.key | wg pubkey > server-public.key
# Basic server config (/etc/wireguard/wg0.conf)
[Interface]
Address = 10.8.0.1/24
ListenPort = 51820
PrivateKey = <server-private-key>
[Peer]
PublicKey = <client-public-key>
AllowedIPs = 10.8.0.2/32
Once connected, access the Hikvision camera at its normal LAN IP:
rtsp://admin:password@192.168.1.64:554/Streaming/Channels/101
Best for: IT administrators who manage the network infrastructure, want full control, and are connecting from devices they personally control. Not practical for sharing access externally.
Alternative 3: Port Forwarding
Port forwarding maps an external port on your router to the camera's internal IP and port 554. It is the simplest approach technically but carries significant security risks.
Pros
- No cloud service — direct connection
- No additional software required
- Low latency (direct path)
Cons
- Camera directly exposed to the internet
- Hikvision CVE-2021-36260 (CVSS 9.8) — RCE if unpatched
- Indexed by Shodan within hours
- Requires router access and public IP
- Does not work behind CGNAT
- Dynamic IP requires DDNS workaround
- No access control beyond camera password
If you use port forwarding with Hikvision cameras, ensure your firmware is fully up to date. CVE-2021-36260 affected hundreds of Hikvision models and allowed unauthenticated remote code execution — meaning an attacker could take over your camera without knowing your password. Many deployed cameras were never patched. Check your firmware version against Hikvision's security advisories before exposing any camera to the internet.
Port Forwarding Setup
If you choose to proceed with port forwarding despite the risks:
- Assign the camera a static IP on your LAN (either via DHCP reservation in your router, or set it statically in the camera's network settings)
- In your router, create a port forwarding rule: external port 554 → internal IP
192.168.1.64port 554, protocol TCP - If you have multiple cameras, use different external ports: 554 → cam1, 555 → cam2, 556 → cam3
- Use a DDNS service (No-IP, DuckDNS) to get a stable hostname if your public IP is dynamic
- Access the stream:
rtsp://admin:password@your-ddns-hostname.com:554/Streaming/Channels/101
Best for: Temporary setups, home labs with non-sensitive footage, situations where you need a zero-cost solution and understand the security tradeoffs. Not recommended for commercial or sensitive deployments.
Comparison: All Three Alternatives
| Property | Hik-Connect | Cloud Relay | VPN | Port Forwarding |
|---|---|---|---|---|
| No Hikvision account needed | No | Yes | Yes | Yes |
| Video off Hikvision servers | No | Yes | Yes | Yes |
| Works behind CGNAT | Yes | Yes | Partial | No |
| No port forwarding required | Yes | Yes | Partial | No |
| Works with VLC / ffmpeg / OpenCV | Limited | Yes | Yes | Yes |
| Share access with third parties | Via app | Yes (token) | No | By IP/password |
| Camera directly on internet | No | No | No | Yes |
| Setup complexity | Low | Very low | Medium–High | Low–Medium |
| Monthly cost | Free | $2/stream | Free–$10 (VPS) | Free |
Access Hikvision Without Hik-Connect
Set up secure remote access to your Hikvision cameras in under 5 minutes. No Hik-Connect account, no port forwarding, no Hikvision servers.
Get Started with TheRelay →Frequently Asked Questions
Is Hik-Connect safe to use?
Hik-Connect functions reliably and provides remote access. The privacy concern is that your camera video may route through Hikvision's cloud infrastructure, which is operated by a company majority-owned by CETC, a Chinese state-owned enterprise. Hikvision has been listed by the US FCC on its Covered List and has been subject to restrictions by multiple governments for use in sensitive installations. For home use with non-sensitive footage, many users find this acceptable. For commercial deployments, government facilities, or any environment with privacy requirements, routing surveillance video through third-party infrastructure you do not control is considered a significant risk. Using a cloud relay or VPN keeps your video on infrastructure you choose.
What is the Hikvision RTSP URL format?
Hikvision RTSP URLs follow this structure:
rtsp://username:password@camera-ip:554/Streaming/Channels/XYY
Where X is the channel number (typically 1 for a single-channel camera, or the NVR input number 1–16+) and YY is 01 for the main stream or 02 for the sub stream. For a standard IPC:
# Main stream
rtsp://admin:yourpassword@192.168.1.64:554/Streaming/Channels/101
# Sub stream (lower bandwidth, better for remote viewing)
rtsp://admin:yourpassword@192.168.1.64:554/Streaming/Channels/102
Can I use Hikvision cameras without the Hik-Connect app?
Yes, completely. Hikvision cameras support standard RTSP streaming independently of Hik-Connect. You do not need a Hikvision account, the Hik-Connect app, or any Hikvision cloud service to access your camera's video stream. You only need the camera's local IP address, your admin credentials, and one of the remote access methods described in this guide. Many users run Hikvision cameras for years without ever configuring Hik-Connect.
How do I find my Hikvision RTSP URL?
The URL follows the standard format above — you mainly need to know your camera's local IP address and admin password. To find the camera's IP:
- Use the Hikvision SADP Tool (free download from hikvision.com) to scan your LAN and list all Hikvision devices with their IP addresses
- Check your router's DHCP client list for a device with a Hikvision hostname or MAC address prefix
- Log into the camera's web interface (navigate to the camera's IP in a browser) and find the network configuration
The default username is admin and the password is either set during initial setup or printed on a sticker on the camera body. The default RTSP port is 554 unless you changed it in the camera's network settings.