V2Ray / Xray Clients
V2Ray and Xray are names you will often see in proxy subscriptions and client ecosystems. For everyday users, the important question is usually which client can import the configuration supplied by a service provider.
Common clients
| Client | Platform | Typical role | Guide |
|---|---|---|---|
| v2rayN | Windows · Linux · macOS | Desktop multi-core client | Detailed setup |
| v2rayNG | Android | Android client | Detailed setup |
| Hiddify | Windows · macOS · Linux · Android · iOS | Cross-platform client | Detailed setup |
V2Ray, Xray and the client are different layers
- Service provider gives you a subscription or node data.
- Client gives you the user interface and profile management.
- Core processes the selected protocols and routes traffic.
A page may say it “supports Xray”, but you should still check which configuration format and protocol types the current client version accepts.
Typical workflow
- Install the client from its official project or store listing.
- Obtain a subscription or profile from your service provider.
- Add the URL or configuration using the client's supported import method.
- Update and check that the nodes are available.
- Select a node and enable the appropriate proxy mode.
- Test a normal website before changing advanced settings.
Compatibility checklist
Before troubleshooting an import problem, check:
- Is the subscription URL still valid?
- Does the client support the provider's output format?
- Is the selected core compatible with the profile?
- Is the device date/time correct?
- Can the client reach the subscription domain?