Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.


In a VLESS configuration, flow selects an XTLS flow-control algorithm for a user or outbound. An effectively empty value selects no Vision flow; xtls-rprx-vision selects Vision in supported transport/security combinations. A blank server user field can inherit the inbound default, so inspect the effective value rather than the blank alone. It is not a bandwidth limit, traffic direction, QoS class, route, or synonym for REALITY.[1][2]
The complete VPN guide maps the whole tunnel. This article isolates one overloaded word so that “flow” in an Xray profile is not interpreted using a router dashboard, firewall log, or network-programming definition.
This guide follows the official documentation listed below and has not been tested end to end on a live client/server pair. Check the schema and supported behavior for your installed versions before applying the checks.
Key Takeaways
flowis an algorithm selection attached to a VLESS client/user configuration.- An effectively empty flow and Vision are different modes; a blank server user field may inherit the inbound default.
- Client and server values must form a combination supported by their exact versions and transport security.
- Selecting Vision does not automatically select TCP, REALITY, routing, or system-wide traffic capture.
- Diagnose
flowonly after reachability and outer security reach the VLESS stage.
Project X documents flow on VLESS user entries and outbounds as the name of the XTLS flow-control algorithm. This article compares an empty value with the common xtls-rprx-vision mode. Current outbound documentation also lists xtls-rprx-vision-udp443, a Vision variant that does not intercept UDP port 443, so these two focus cases are not an exhaustive list.[1][2]
The value is a literal configuration token. “Vision,” “XTLS,” an app toggle, and xtls-rprx-vision are not necessarily interchangeable strings. Importers may map a friendly label to the token, but diagnosis must inspect the effective configuration created for the exact client version.
Figure key: 1 is the effective flow after resolving any inbound default; 2 is selection under the implementation's compatibility rules; 3 is an empty flow; 4 is xtls-rprx-vision. The branches show configuration choices, not packet direction, performance ranking, or a complete protocol stack.
flow mean?For a VLESS outbound, an absent or empty flow selects the standard documented proxy mode rather than Vision. On the server, current Xray configuration has an inbound settings.flow default: a missing or empty users[].flow inherits that value. If the default is xtls-rprx-vision, setting a user's field to "" does not disable Vision. Only an effectively empty value means no Vision selection.[1][2]
Read the inbound default and user entry together, then compare the resolved server value with the client outbound. A blank GUI box or omitted subscription field alone does not prove that the server expects no flow. Check the exact installed schema and importer output; older versions and other clients may handle defaults differently. Empty flow does not mean no traffic, TLS, transport, or security, and it does not ask the software to find the fastest mode.
Empty can be the correct value for a standard supported VLESS-over-TLS combination. Adding Vision to “optimize” a working profile without checking compatibility changes the protocol behavior and may make both ends disagree.
xtls-rprx-vision select?xtls-rprx-vision selects the Vision flow algorithm described by Project X. It is part of a specific combination of VLESS, transport, and security settings, not an independent tunnel protocol. Official inbound documentation lists supported network and security combinations and notes version-dependent details.[1]
Vision's purpose and behavior should be taken from current Project X documentation for the installed versions. A token appearing in a copied URI does not prove that the client implements it, that the server permits it for that user, or that the surrounding transport matches.
The VLESS, REALITY, and XTLS Vision layer guide separates the proxy protocol, transport-security behavior, optional flow, and system routing. That separation prevents the common claim that enabling Vision automatically enables REALITY or turns an application proxy into a device-wide VPN.
Vision is only one value in a tuple of VLESS, transport, and security settings that both endpoints must support. Before checking that tuple in detail below, decide whether you want to maintain it yourself.
Keeping it aligned also means rechecking flow after every client or core upgrade on both ends. Unless you are testing Vision itself or need routes into a private network, AethoVPN takes that whole tuple off your list: sign in with an email code on the Windows, Debian/Ubuntu x64 .deb, or Android app and choose a location, while Mac, iPhone, and iPad get their configuration from the website setup wizard and require Pro or Premium.
What remains is the question this article raises about application proxies versus device-wide routing: is the app you care about inside the tunnel? Turn on global mode, which sends traffic from every app on the device through the VPN, confirm the browser's exit with the IP checker, and then retry the task in that app, because the browser result does not show what another app did. With global mode off, sites in your own region are reached directly, which helps when a local site rejects foreign IPs but also means that local traffic will not show the VPN exit.
Because the product names no protocol, a working AethoVPN connection is no reference value for your own server, whose flow still has to match what its owner documented. Start the 3-day free Pro trial if you choose managed access; it is available once per user.
flow?Start with the VLESS client and server user entries. The selected flow must be allowed for that identity and supported on both endpoints. Next check the network/transport mode and the selected transport security. Compatibility is a tuple, not a single green checkbox.
| Configuration dimension | Question | What it does not prove |
|---|---|---|
VLESS id | Is the intended user authorized? | Which flow is compatible |
VLESS flow | Is empty or Vision selected? | That REALITY is enabled |
| Network/transport | How are proxy messages carried? | User authorization |
| Security | Which supported protection wraps the path? | System-wide capture |
| REALITY fields | Do key, name, short ID, and target-related checks agree? | Route or DNS success |
| Routing/TUN | Which application traffic enters and exits? | Flow negotiation |
The current official combinations are TCP with TLS/REALITY, or VLESS Encryption. With VLESS Encryption, Vision is not restricted to TCP, but a non-TCP transport does not gain TCP Splice; with TCP, Splice is still conditional on the documented environment and path. Ordinary outbound xtls-rprx-vision intercepts UDP/443 to encourage standard HTTPS; the outbound xtls-rprx-vision-udp443 variant does not. Neither value guarantees speed or QUIC success.[1][2] Freeze both endpoint versions and confirm their exact supported tuple before applying a sample.
A compatible VLESS tuple still does not prove which device traffic enters the proxy. Compare TUN capture with system proxy settings when application coverage is the remaining question; keep that decision separate from flow compatibility.
A server can authorize a UUID but reject or fail the associated flow combination. Likewise, the outer REALITY stage can succeed while the later VLESS/flow behavior fails. Keep timestamps and stage-specific logs so one success is not used as proof for the next layer.
flow not mean?Networking tools use “flow” for many concepts: a five-tuple of source/destination addresses and ports, one direction of a session, a firewall state entry, a QoS classification, a bandwidth meter, or application traffic over time. The VLESS field does not inherit all those meanings.
It does not cap speed, prioritize video, select the least congested server, define upload versus download, or route one application outside the tunnel. It does not decide whether DNS is local or remote. It does not name a destination, a port, or a REALITY target.
It also does not provide user authentication.[3] The VLESS id or UUID selects an allowed user. What the VLESS UUID authenticates explains that distinct gate. Changing flow cannot repair an unknown user entry.
Both endpoints need compatible behavior for the same session. If the client applies Vision while the server expects an empty flow, or the server user is configured for Vision while the client uses a standard path, their parsing and handling assumptions diverge. The result can be an early disconnect, protocol error, or connection that reaches one stage but cannot carry useful data.
An unsupported combination can fail even when both sides contain the same literal token. Client/server versions, network type, and security mode matter. A configuration validator may reject it before start; another implementation may start but reject the attempt at runtime.
Do not infer a flow mismatch from every performance complaint. A connection that carries traffic but is slow may involve latency, packet loss, congestion, CPU, MTU, application behavior, or destination throttling. Establish the configured mode and error stage before changing it.
Freeze the exact client and server versions, effective configurations, one timestamp, and the first error. Confirm address and port reachability, then confirm that the selected transport-security layer completes far enough to evaluate VLESS. If REALITY authentication fails first, changing flow hides rather than solves the first problem.
Compare the inbound settings.flow default, server users[].flow, and client outbound side by side; resolve inheritance before comparing values. Keep id, flow, network/transport, security, and relevant REALITY settings in separate rows. Verify the literal value and whether the exact versions support that tuple. Inspect generated configuration after subscription import because a UI can omit or normalize fields.
Write one hypothesis: “Both endpoints authorize this user, but the client selects Vision while the server user has an effectively empty flow after resolving the inbound default.” Change only the flow on the incorrectly configured side to the intended documented value, reload safely, and repeat the same bounded request. If the failure moves to a later stage, preserve that evidence and diagnose the new stage separately.
The VLESS REALITY failure checklist covers the sequence from parsing through routing. A known-good configuration from another server is comparison evidence, not a source of credentials or proof that its flow tuple fits this server.
Treat it as a compatibility change, not a cosmetic edit. Inventory affected users, clients, versions, transports, and security settings. Confirm the supported target tuple and a rollback configuration. Update a small authorized test group first and capture both handshake and application-traffic evidence.
If clients cannot be updated atomically with the server, use only an overlap mechanism explicitly supported by the implementation. Do not invent duplicate fields or depend on unknown-field fallback. Separate user entries can sometimes stage a migration, but that changes identity and policy inventory and must be planned accordingly.
After rollout, verify the effective server reload, current client import, expected flow value, authenticated session, and a known destination. Monitor failure categories rather than storing full profiles. Remove temporary users or compatibility paths once the planned window closes.
Keep a version-aware record. A future upgrade can change accepted combinations or defaults. Retest the tuple during upgrades instead of assuming that a connection label means the same behavior forever.
flow selects an XTLS flow-control algorithm for a user/outbound.flow mean no encryption?No. Flow selection and transport security are separate. An empty flow can still be used with a supported TLS-protected configuration.
xtls-rprx-vision a VPN protocol?No. It is an XTLS flow selection used with supported VLESS combinations. Device-wide VPN behavior also requires traffic capture and routing outside this field.
They must use a mutually supported, correctly configured combination. Compare the client outbound with the effective server user flow, including the inbound default, for the exact versions.
No. REALITY is a separate transport-security configuration with its own key, server-name, short-ID, and target-related fields.[4]
Do not treat it as a generic speed switch. First confirm compatibility and measure the actual bottleneck; changing protocol behavior can break a working session.
No. The UUID can authorize the user while the selected flow combination remains incompatible. Each check must pass in its own layer.
flow?The source may intend an empty flow, the format may use a default, or the importer may not support the field. Inspect the authorized source and effective generated configuration before editing.
Disclaimer: This article is general technical information for authorized configuration. Follow version-specific documentation and do not use copied profiles to bypass network or service policy.
Sources:
Sources checked 8 October 2026.
Related Articles:
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.