Shadowrocket Config File Structure Explained: What Goes in [General], [Rule], [Host], and [URL Rewrite]

1. Understand the difference between config files, server details, and routing modes

.conf is a text-based config file. Section names appear in square brackets, followed by the settings for that section. Putting rules in [General] or DNS settings in [Rule] will not produce the intended configuration. When reading a file, identify the section first, then check each line’s syntax. Don’t search for a domain and edit it without checking the surrounding rules.

This guide assumes you already have your own service provider and subscription. Server details in Home describe the connection destination, port, and authentication method; a file in Config describes how requests are routed. Importing a config file does not fill in missing server details, and updating a server subscription does not update the currently selected config file.

• Home: Check your existing server details, choose a connection destination, and review Global Routing.
• Config: Import, select, and edit config files. A file appearing in the list does not mean it is selected.
• Settings: Adjust app settings. For example, use Settings → On Demand to manage conditions for connecting on demand. On Demand does not replace routing rules.

2. [General]: Set global options as key-value pairs

[General] uses the format key = value. Use this section for global settings such as DNS, not for DOMAIN-SUFFIX rules. When troubleshooting, note the existing value and change one setting at a time. Changing DNS, rules, and the connection destination together makes it difficult to identify what caused the result.

[General]
dns-server = system

This example tells DNS to use the system-provided resolver. It is not a one-size-fits-all setting: if the current network has a DNS issue, keeping system will not fix it automatically. To specify another resolver, use an address you have confirmed works and enter it in a format supported by the app.

Don’t add every setting you find online just to make the config look complete. Keep only settings you can explain. Before changing behavior such as IPv6 or timeouts, check the in-app documentation and valid values for the relevant parameter instead of reusing numbers from an unknown source.

3. [Rule]: Rules are checked from top to bottom; put FINAL last

[Rule] determines which policy a request uses. Rules are checked in order, and the policy for the first matching rule applies. Put narrower exceptions before broader rules. The example below shows syntax only; replace example.com with a domain relevant to your needs.

[Rule]
DOMAIN,login.example.com,DIRECT
DOMAIN-SUFFIX,example.com,PROXY
IP-CIDR,192.168.0.0/16,DIRECT,no-resolve
GEOIP,CN,DIRECT
FINAL,DIRECT

In this example, login.example.com matches the first line and uses DIRECT, while www.example.com matches the second line and uses PROXY. If you swap the first two lines, the suffix rule will match the login domain first, making the exception in the first line ineffective.

4. [Host]: Domain mappings are not proxy rules

[Host] maps a domain to a local address. It answers “Which address does this name resolve to?” while [Rule] answers “Which policy should this request use?” They serve different purposes. After adding a mapping, check which rule the request matches.

[Host]
device.example.com = 192.0.2.10

192.0.2.10 is a documentation example address, not a real device you can connect to. This example only shows the “domain equals address” format. Copying it will not make a website load. Use an address you have verified and confirm that it is reachable on your current network.

• On the left, enter a domain without https:// or a /path.
• A mapping does not change the domain in the browser’s address bar or automatically change HTTPS certificate requirements.
• A wrong address can cause a connection failure or certificate mismatch. Don’t hide a mapping error by disabling certificate verification.
• If the app uses another resolution method or reuses an existing connection, the result may not change immediately. Check again with a new connection and review the connection log.

If you don’t need a specific mapping, you can leave this section out. If you add a temporary entry to troubleshoot an issue, remove it or restore the original value after testing. Otherwise, an outdated mapping may continue to point to an old address after the remote service changes.

5. [URL Rewrite]: Rewrite requests based on URL patterns

[URL Rewrite] defines URL matching and rewriting; it does not select a proxy policy. A typical entry includes a match expression, a destination URL, and an action. The example below redirects an HTTP URL, showing how to match the start of a string, escape the dot in a domain, and use 302 for a temporary redirect.

[URL Rewrite]
^http://example\.com/ https://example.com/ 302

In the example, ^ anchors the match to the start of the string, and \. matches a literal dot. An overly broad expression can affect unrelated URLs. If the destination URL matches the original rule again, it can also cause a redirect loop. HTTPS requests are encrypted, so a rule alone cannot necessarily read and rewrite their paths. Whether additional settings are needed depends on the specific method. This guide does not cover HTTPS decryption settings.

6. Import, edit, and enable a file in Config

Keep a working copy of your existing file before importing or editing a duplicate. Use a remote config URL only if you have verified its source, and make sure it returns config text rather than a login page or web instructions. URLs containing tokens are sensitive; don’t include them in public screenshots or support requests.

1. Keep the original

   Open Config, note the name of the currently selected file, and save a copy of its original text. If testing fails, restore the original file instead of layering changes onto an unknown state.

2. Import a file

   In Config, tap “+” in the upper-right corner, enter a config URL you already have, then tap Download. After importing, check the file in the list and verify its contents. Don’t mistake a server subscription URL for a .conf URL.

3. Edit the text

   In Config, tap the info button beside the file you want to edit, then open Edit Plain Text. Check the section names before editing line by line. If the interface uses localized labels, choose the corresponding text-editing option shown in your app.

4. Select the config file

   After saving, return to Config, tap the target file, and confirm that it shows as selected. Go to Home → Global Routing and select Config. Saving the text alone does not switch another mode to Config.

5. Test again

   Confirm that a connection destination is available in Home, then reconnect and test one target domain and one unrelated domain. Check the destination, policy, and matching rule in the connection log. If needed, restore the original file for comparison.

A remote config update may overwrite local edits. Save a separate copy of any rules you want to keep and compare the sections after an update. Before sharing a config file, remove server details, authentication information, and private addresses one by one; hiding only the filename is not enough.

7. Verify the result in Global Routing and the connection log

“Imported” and “currently routing traffic according to the file” are not the same state. To test the [Rule] examples in this guide, first confirm that Global Routing is set to Config. Other modes serve different purposes; results after temporarily switching modes do not prove that the rules in the file are active.

Test observable results rather than checking only whether the connection toggle is on. Browser cache, existing connections, and how an app makes requests can all affect the result. After making a change, send a new request and check the connection log. The table below suggests troubleshooting checks; it does not guarantee how every app will behave.

After checking, you should be able to identify the file in use, the rule matched by a request, and why that policy was applied. Once you can explain all three, you can add more complex rules. If you don’t need mappings or rewrites, leave those sections empty or omit them.