Back to Blog

Xray vs sing-box vs Mihomo: Which VLESS Client Core Should You Choose in 2026?

Technical Editorial Team · Published October 3, 2026 · Updated November 13, 2026

Xray, sing-box, and Mihomo are three common proxy cores. All support VLESS, but their design priorities and day-to-day experience differ.

Xray emphasizes compatibility with VLESS, REALITY, and related technologies; sing-box brings DNS, routing, and TUN into one core; Mihomo stands out for its established Clash rules ecosystem, proxy groups, and automatic server selection.

Most users do not need to study proxy cores before choosing a client. What matters more is a stable connection, correct subscription imports, support for the server’s complete configuration, and the ability to select a suitable server automatically.

Understanding the differences also helps explain why clients can behave differently when connecting to the same VLESS server. For app recommendations, see our VLESS client guide. This article compares the cores underneath them.

Xray: closely tied to VLESS and REALITY development

Xray is a major home for original development and a principal implementation of technologies including VLESS, REALITY, XTLS Vision, and XHTTP. New protocol and transport features generally reach Xray first, making it a good fit for users who prioritize the latest features and native compatibility.

Xray supports DNS, rule-based routing, and load balancing, but its main strength is native support for new VLESS-related technologies. v2rayN and v2rayNG are representative clients in this ecosystem.

Who is it for? Users who mainly use VLESS, REALITY, Vision, or XHTTP and place particular value on Xray configuration compatibility.

sing-box: integrated networking features

sing-box is a networking core that supports multiple proxy protocols. Alongside VLESS, it provides DNS, rule-based routing, TUN, and automatic server testing.

A client can use these features to manage different kinds of traffic within one core. For example, it can connect directly to mainland Chinese websites, proxy other destinations, or select different servers according to rules. The actual path depends on the configuration.

Clients such as Karing use technologies from the sing-box ecosystem. That does not mean every version has exactly the same features as official sing-box.

sing-box has its own configuration format. Even when Xray and sing-box connect to the same VLESS server, their full configuration files are not interchangeable.

sing-box supports VLESS, REALITY, and XTLS Vision, but currently does not support XHTTP.

More features do not necessarily mean faster connections. DNS resolution, routing, connection establishment, and client configuration can all affect the result.

Who is it for? Users who need flexible DNS, rule-based routing, TUN, and multiple protocols, with a client that accepts sing-box configurations.

Mihomo: established Clash rules and automatic selection

Mihomo builds on the configuration and management model of the Clash ecosystem. It supports VLESS, REALITY, XTLS Vision, and XHTTP, and can organize servers into policy groups that work with routing rules. Transport settings must still match the server.

For example, a properly configured Mihomo subscription can:

  • Connect directly to mainland Chinese websites and proxy other destinations according to rules.
  • Group servers by regions such as Hong Kong, the United States, and Japan.
  • Test servers periodically and select nodes based on the results.
  • Select a backup node for new connections after detecting that the current server is unavailable.
  • Use designated proxy routes for particular websites or services.

If the provider includes these policies in the subscription, users do not need to configure every server and rule individually. Importing a single VLESS link, however, may not include the complete policy.

Clash Verge Rev is a representative desktop client in this ecosystem. Mihomo’s strength goes beyond protocol support: Clash-style rule sets, proxy groups, node testing, and failover form an established workflow.

Who is it for? Users with Clash-style configurations who need rule-based routing, automatic server selection, or management of many proxy nodes.

Xray, sing-box, and Mihomo feature comparison

FeatureXraysing-boxMihomo
Main focusVLESS and related technologiesIntegrated protocols and networking featuresClash rules and proxy groups
VLESS / REALITYSupportedSupportedSupported
XTLS VisionSupportedSupportedSupported
XHTTPSupportedNot supportedSupported
DNS and rule-based routingSupportedSupportedSupported
TUN traffic handlingBuilt-in TUN inbound; check version and platform integrationBuilt-in TUN inboundBuilt-in TUN support
Automatic server selectionRouting balancers and observatory mechanismsURLTestProxy groups such as url-test and fallback
Common configuration formatJSONJSON, with a different structure from XrayYAML
Main strengthXray configuration and new-feature compatibilityFlexible network configurationEstablished rule and node management

This table covers common core capabilities. Availability also depends on the client implementation, operating system permissions, and core version. Support for individual features does not mean every combination of transport, security, and flow settings can be enabled together.

Xray’s current official documentation includes a TUN inbound. On Android and iOS, an external app must supply the system TUN file descriptor; it cannot operate independently. Check whether the client actually uses this integration path.

The three cores overlap considerably. Their differences lie more in configuration, feature combinations, and how clients use them. Prefer the subscription format your provider prepares for your client rather than manually converting a complete configuration.

Which is faster: Xray, sing-box, or Mihomo?

There is no universal speed ranking for every network.

Even with the same server, protocol, and transport, download speeds depend on server bandwidth, ISP routes, congestion, and packet loss. Everyday responsiveness also involves more than download throughput.

How quickly a website opens, whether connections recover promptly after switching apps, and whether DNS returns results in time all affect the experience. It helps to distinguish:

  • Connection responsiveness: The time from starting a request to establishing a connection and beginning to load the website.
  • Sustained throughput: The transfer rate after connection establishment, while downloading files, streaming video, or transferring data continuously.

A client setup that opens websites faster will not necessarily win every download test. Useful comparisons cover responsiveness, stability, and sustained throughput while keeping the device, network, server, core versions, and test conditions consistent.

Which core should you choose in 2026?

Xray: prioritize VLESS compatibility

Consider Xray first if you mainly use VLESS, REALITY, XTLS Vision, or XHTTP, especially if you need new Xray-specific features. Confirm that the client’s bundled core version supports the provider’s configuration.

sing-box: flexible network configuration

sing-box offers extensive DNS, TUN, rule-based routing, and multi-protocol features for users with specific networking needs. That integration does not mean better performance on every network.

In complex network environments such as mainland China, DNS, address selection, connection fallback, and loading rule resources can all affect the experience. Assess a sing-box client by its actual connection behavior and how well its configuration is maintained.

Mihomo: our current recommendation for everyday VLESS users in mainland China

For users who mainly use VLESS in mainland China and need smart routing and automatic server selection, we currently recommend Mihomo. Its established Clash ecosystem makes it convenient to manage proxy groups, routing rules, and node selection policies in one configuration. In practice, its DNS resolution, IPv4/IPv6 connection handling, and routing policies better suit mainland China’s complex network conditions and our current needs.

Technical references

These documents were checked on November 13, 2026. Check the version you use for subsequent changes in support.

Further reading