In XrayUI, you can create your own custom geosite tag files and include them in the final compiled xrayui geodata file used by Xray. This allows you to define your own domain groups (like blocklists, allowlists, or custom routing sets) in a clean and reusable way.

Where the File lives

XrayUI compiles a single custom geosite file named xrayui located at:

/opt/etc/xray/xrayui

Where the Tag Files lives

XrayUI use so called tag-files that you maintain via the Geosite Tag Manager in the XrayUI.

/opt/share/xrayui/data

[!CAUTION] There is a limit in characters to submit from the web interface, so big lists are not allowed. If you need to place a very big list, just create your text file in this directory manually.

This file is automatically rebuilt through the web interface whenever you make changes to your custom tag files.

What is a Custom Tag File?

A tag file is a plain-text file containing a list of domains. It's similar in structure to the community-maintained geosite files (like v2fly/domain-list-community).

For example, you might create a tag file named mystelist, containing your own selection of domains.

Once added and compiled, you can refer to this tag in your Xray configuration using the ext token like so:

ext:xrayui:mystelist

Breakdown of the token:

• ext tells Xray to use an external geosite source.
• xrayui is the compiled file name.
• mystelist is the tag you defined.

How to Create One via the Web Interface

Follow these steps:

• Go to File Manager in the web interface in Routing section.
• Click Local Files button.
• Choose Create New File -This will create a new tag file, not the compiled xrayui file itself.
  • For example, name it mystelist.
  • Add your list of domains in the file, one per line.
  • Format is the same as in the community rules.
• Click Compile.
• This triggers the rebuild of the unified xrayui file.
• Your tag will now be available via: ext:xrayui:mystelist.

[!NOTE] You can get the inspiration from the domain-list-community repository.