Home
Main connection dashboard. It shows tunnel state, quick connect behavior, live route information, import entry points, and the Inject workflow when you want fast payload-driven changes.
Understand the app before you tune it.
This documentation center explains what each part of v2ray injector does, how the app uses the Xray stack, which links and transports it accepts, where public servers come from, how CDN-based routing is organized, and how advanced features such as Socket Custom and V2K should be used in production.
What the app is
Custom Xray client
v2ray injector is an Android client built on top of Xray behavior, plus custom transport work such as Socket Custom and the V2K family. It is not only a generic VPN wrapper.
Two usage layers
New users can stay with catalog servers and preset configs. Advanced users can switch to manual mode, raw JSON, `.v2k` files, Store listings, and transport-specific tuning.
Protocols and transports
The app supports standard Xray protocols and transports, then extends them with workflow-specific features such as HTTP RAW payload handling and carrier-sensitive V2K fallbacks.
Catalog + personal configs
You can use official catalog servers, public externally sourced servers, imported links, or your own custom/personal entries without losing access to the same Config workflow.
What each part of the app does
Inject
Fast profile-oriented flow. Best when you want to pick a server, apply a config quickly, and edit only the most common payload or compatibility values instead of the full transport schema.
Servers
Full browser for official catalog servers, public servers, and personal servers. Use it when you need to change country, inspect categories, ping, test, or manage your own imported entries.
Config
Advanced configuration workspace. This is where manual transport values, Socket Custom controls, V2K knobs, `.v2k` import/export, Store publication, and raw JSON editing are managed.
Store
Marketplace and creator flow for `.v2k` content. Use it to browse published configs, redeem or import them, and publish your own packages when creator access is enabled.
Personal servers
Personal entries are the place for your own links, raw JSON imports, and custom tunnels that do not need to stay attached to the official catalog.
Recommended flow for most users
Select a server first
Pick an official or public server that supports the transport you need. If you already have a personal link or JSON, import it and let the app create a personal entry for it.
Apply a compatible config
Configs are not only cosmetic presets. They can depend on transport, security, port, and CDN type. If a config does not match the selected server, the app may ask to switch to a compatible route.
Open Config only when needed
Use the Config tab for manual tuning, JSON editing, `.v2k` sharing, Socket Custom payload work, or V2K mode changes. If a route already works, avoid changing advanced fields casually.
Use advanced modes intentionally
Standard WS, gRPC, XHTTP, or direct TLS paths should be your first choice. Socket Custom and V2K are problem-solving tools for specific networks, gateways, and restrictive carrier conditions.
Open the right guide for the job
Protocols and accepted links
Learn the difference between protocol, transport, and security layers. Includes VLESS, VMess, Trojan, Shadowsocks, WireGuard, and which link types the app can import directly.
Marketplace and `.v2k`
Detailed guide for `.v2k` files, editable versus protected import, Save/Publish flows, open versus protected Store listings, and Creator Studio behavior.
Socket Custom
Detailed guide for HTTP RAW payload workflows, supported markers, handshake controls, examples, and the main operational caveats.
CDNs
Understand how the app labels Cloudflare, Fastly, CacheFly, Google Cloud, CloudFront, Azion, Bunny, and direct/custom routes, and how configs interact with CDN matching.
Public servers
Explains official/internal servers versus public externally indexed servers, where public Shadowsocks and other public links come from, and the operational risks of using them.
V2K
Complete guide for V2K `stream`, `poll`, and `carrier-poll`, field meanings, server requirements, sharing, and production baselines.
Things to understand before troubleshooting
Configs and servers are different things.
A server gives you the host, route family, ports, and path capabilities. A config tells the app how that
route should be used. One server can have multiple configs with different behaviors.
Advanced modes are network-sensitive.
Socket Custom and V2K behavior can vary a lot across carriers, CDNs, and gateways. A working preset on
one operator can fail on another without any code bug in the app itself.
Public servers are not operated by the app team.
The app can surface externally indexed public servers, but availability, trust level, and performance of
those routes can change without notice.
Need the deep protocol pages?
Open the dedicated guides for Socket Custom, CDNs, public servers, or V2K when you want the full field list, examples, and operational caveats.