These configuration contracts describe OneXray 26.9.3. See upgrading for changes from previous versions. Connection backup is a separate restore format, not a fourth configuration-import type.

OneXray supports outbound, Custom Routing and Raw JSON imports. Each import type has its own fields and requirements; choose the type that matches the task.

Capability	Behavior
Outbound / Custom / Raw import	Supported
Custom domain, target IP, port, network	Supported
Custom local DNS via app-dns-direct	Supported
Custom protocol and localOS	Supported
Smart/Custom FakeDNS switch and app-dns-fake	Supported; off by default
Advanced Custom DNS, sniffing, auxiliary outbounds and local inbounds	Supported through a separate JSON template
FakeDNS recovery on a newly generated Raw inbound	Enabled when Raw declares a FakeDNS server or pool; existing sniffing stays unchanged
GitHub proxy priority with Microsoft bypass	Supported; precedes direct rules

Older versions may not support every field described here. If an option is missing or a supported field is rejected, update the App first. Never silently drop conditions to make a configuration import; explain the limitation and agree on an alternative if the user must keep an older version. Raw JSON is not an automatic workaround for missing native integration.

Traceable sources

• The configuration contracts define the App import boundaries. Example validation provenance is recorded in the manifest below.
• Get the App through the installation guide.
• Core used for this documentation’s example checks: libXray commit c145d94071088cebd445d7b0f4b1bea35732011e, Xray-core v1.260327.1-0.20260908222543-52a412d9e2f5.
• Machine-readable example manifest records import types, dependencies and replacements per file.

The current upstream manual may describe fields newer than an installed App’s Core. OneXray’s envelope and ownership rules take precedence for App imports; protocol validity is decided by its bundled libXray. Do not mix syntax from unrelated clients or old VMess QR-code JSON into these documents.

Limits and required data

Ordinary and Advanced Custom Routing share up to three saved profiles, each with 1–3 leading empty entry slots and a unique name of 1–32 characters. Advanced templates may append auxiliary outbounds. The types do not convert during editing. New Raw configurations are limited to three; existing older Raw records above the limit remain usable, with Add hidden.

Normal mode needs actual nodes already in the App. Group/automatic selection must have enough eligible distinct nodes for the requested entry count. A fixed individual server uses that server. Raw JSON must contain its own actual proxy configuration; it does not borrow nodes from the normal-mode selection.

Node and Raw examples use reserved example domains and dummy IDs. Replace them with provider-supplied values. They are templates, not free working servers.