How Subscription URLs Work

Overview

Sharing proxy configurations one link at a time does not scale, so the ecosystem converged on subscriptions: one URL that returns the whole current config list in a single response. Your client fetches that URL, parses the body, and replaces its server list. When an endpoint dies and the publisher updates the list, a refresh in the client picks up the change without any manual importing.

What the response looks like

Two payload styles dominate:

• Plain text - one share URI per line, such as vless://..., trojan://... or hysteria2://... lines.
• Base64-wrapped - the same line list, encoded as one base64 blob. See how base64 config encoding works.

Well-behaved clients accept both transparently. HiddenIO's feed at /sub/all returns the raw line format and supports ?format= parameters for structured variants such as Clash YAML or sing-box JSON.

Formats and filters

A single source list can be rendered into many client formats without changing the endpoints themselves:

• raw - original share links, one per line.
• base64 - the wrapped form used by older V2Ray clients.
• clash / mihomo - YAML proxy lists for Clash-family cores.
• sing-box - a JSON outbound array.

Feeds can also be filtered, for example ?protocol=vless for a single protocol. The subscription converter performs the same conversions on demand for any URL you already have.

Limitations

A subscription is only as trustworthy as whoever publishes it: the operator can change, log or inspect every endpoint you connect through. HiddenIO aggregates publicly published configs and cannot guarantee that listed endpoints work or are safe - review sources before subscribing.