GeoData provides rule-set files used by Xray-core expressions such as:
geosite:CN
geoip:CNOneXray has two built-in GeoData files:
| Name | Type | Source |
|---|---|---|
geosite |
domain |
v2fly/domain-list-community latest dlc.dat |
geoip |
ip |
v2fly/geoip latest geoip.dat |
Custom GeoData#
Custom rule sets require:
| Field | Meaning |
|---|---|
| Name | Unique name. It becomes the file base name and rule prefix target. |
| Type | domain for geosite-style data or ip for geoip-style data. |
| URL | Download URL for the .dat file. |
When a custom rule set is added or updated, OneXray downloads the .dat file, asks the host core API to count categories and rules, saves the .dat file, and saves a generated JSON summary.
Auto Update#
GeoData auto update is configured on Auto Update. System GeoData and custom GeoData are checked separately from subscription refresh but run from the same update service.
Sharing and Backup#
Custom GeoData can be shared as an onexray:// link containing its type and HTTPS download URL. The receiving app downloads and validates the .dat file; the file itself is not embedded in the link.
When a shared Outbound, Xray Profile, Full Config, or Raw Json references custom GeoData using ext:<Name>.dat:<Code>, OneXray places matching GeoData links before the config link.
For a complete offline migration, use Backup and Restore, which includes custom GeoData database rows, .dat files, and generated .json summaries.
iOS and iPadOS#
Very large rule-set files can increase memory usage. If the VPN fails to start on iOS or iPadOS, use smaller GeoData files or fewer routing rules.