piapia123
en

RTSP Camera URL Parser and Builder

Web

Everything runs locally in your browser — nothing is uploaded

Input
Drop a file here to load its contents
Output

Both directions: paste an RTSP URL to break it into fields (scheme, username, password, host, port, path, query), or build one from the options. ⚠️ The password is the tricky part: its @ : / ? # must be percent-encoded, or @ truncates the host and : splits username from password. The tool encodes when generating, but only once — if you paste a password already written as p%40ss, it is left alone, otherwise it would become p%2540ss, a password that fails silently. Common path templates for Hikvision, Dahua, Uniview and ONVIF are built in. Everything runs locally; passwords are never uploaded.

Features

  • Parse an RTSP URL into host, port, username, password, path and query fields
  • Build a URL from options, with main / sub / third stream and channel
  • Transport selectable as TCP / UDP / multicast (written as transportmode)
  • Built-in path templates and notes for Hikvision, Dahua, Uniview and ONVIF
  • Percent-encodes special characters in the password, exactly once
  • Warns when the input is already encoded, so %40 does not become %2540
  • All local, so passwords never leave your browser

How to use

  1. Choose Parse and paste an RTSP URL, or Generate and fill the options
  2. When parsing, check host, port and path field by field
  3. When generating, pick brand, stream, channel and transport
  4. Copy the whole URL, or copy a single field from its row

FAQ

What if the password contains @ or a colon?
It must be percent-encoded: @ as %40 and : as %3A. Otherwise @ is read as the separator between user info and host, truncating the host, and : is read as the separator between username and password, shifting both. This tool encodes automatically when generating.
Why was my password p%40ss not encoded again?
Because that is already an encoded form. Encoding it again would turn % into %25, producing p%2540ss — the device would decode p%40ss rather than p@ss and fail to connect, with no warning. So the tool detects %XX and uses the value as-is, with a note.
Why do the paths differ between brands?
There is no standard RTSP path. Hikvision combines the channel, a zero and the stream number (main 101, sub 102); Dahua uses /cam/realmonitor?channel=1&subtype=0; Uniview commonly uses /media/video1; ONVIF URIs are usually returned by the device GetStreamUri. The tool shows common forms; the device manual is authoritative.
Is transportmode a standard parameter?
No. It is a URL parameter supported by some devices (such as Hikvision) to pick unicast or multicast. RTSP transport TCP versus UDP is normally negotiated by the client at SETUP with RTP/AVP/TCP or RTP/AVP and cannot be expressed in the URL, so both TCP and UDP are written as unicast here.

Related tools

URL Parser

Web

Parse a URL into scheme, host, port, path, query parameters and fragment, with each parameter shown raw and decoded. Runs entirely in your browser.

cURL Toolbox (code / parse / build)

Web

Turn a curl command into seven languages of code, or break it into method, headers and body fields; or build a curl command back from an HTTP request.

User-Agent Parser

Web

Parse a user agent into browser, version, OS, device type and engine, and see which rules matched. Pattern matching only. Runs entirely in your browser.

HTTP Status Codes

Web

Look up an HTTP status code for its meaning, 1xx–5xx class, typical uses and common traps. Runs entirely in your browser.

MIME Types

Web

Look up a MIME type from an extension, or the default extension for a media type. Common types only. Runs entirely in your browser.

.gitignore Generator

Web

Generate a .gitignore from language, framework, editor and OS templates. Sections are merged and duplicates removed. Runs entirely in your browser.

← Back to all tools