Shadowrocket vs Stash: Which iPhone Proxy App Should You Choose?

Choosing an iPhone proxy app is not just a question of which one has more settings. Your existing subscription, the configuration format it uses, the way you want traffic routed, and how much troubleshooting you are comfortable doing all matter. A familiar interface can make daily use easier, while a configuration model that matches your existing setup can reduce conversion work and unexpected behavior. The practical comparison is therefore about fit: what you need to import, what you want to control, and how you will confirm that traffic behaves as expected.

At a glance

This guide helps iPhone users assess whether Shadowrocket fits their setup and preferences. Check subscription compatibility, decide whether you want rule-based routing or a simpler global mode, and test one change at a time. The examples assume you already have your own service and subscription; they do not provide or recommend connection services. Use the criteria below to choose an app based on your actual configuration needs rather than a feature count alone.

1. Start with your existing configuration

Before choosing an app, identify what you already have. A subscription is not simply a list of app preferences: it can provide connection entries and, depending on the service and format, may also provide configuration information. The fact that a subscription URL can be pasted into an app does not guarantee that every setting, rule, or policy will be interpreted identically. Compatibility depends on the formats and features your configuration actually uses.

Make a short inventory before installing or switching anything. Note whether you have a subscription URL, individual connection details, a configuration file, or some combination. Then check which protocols and rule behaviors your setup requires. Do not share a subscription URL with anyone while testing; it can contain account-specific access information. If you are unsure what a particular format supports, ask the provider you already use for the relevant compatibility details.

Subscription: Is it a URL you refresh, or a set of connection details that you maintain yourself?
Configuration: Does your workflow depend on a separate rule configuration file, or are a few built-in routing choices enough?
Protocols: Which protocols are actually used by your existing entries? Confirm support before migrating.
Maintenance: Do you expect to edit rules, or do you mainly want to select a working connection and turn it on?

Shadowrocket lets users add their own connection details and subscriptions from Home. To import a subscription, tap the “+” button in the upper-right corner of Home, choose Subscribe under Type, enter your own subscription URL, and save. Confirm that the expected entries appear before changing routing settings. If your current setup depends on a file, open Config and verify that the intended configuration is selected. An imported file and an imported subscription are not interchangeable: one may define how requests are handled, while the other may supply connection entries.

Subscription check

Entry point: Home → “+” → Type → Subscribe
Input: Your own subscription URL
After saving: Confirm that expected entries appear
Refresh: Use the subscription’s normal update process

Do not treat a successful import as proof that every rule or policy has transferred.

Configuration check

Entry point: Config
Selection: Check the active configuration
Routing mode: Home → Global Routing → Config
Test: Use a new request after changing settings

The Config screen and Config routing mode are related, but they are not the same control.

2. Choose the routing style you need

A useful comparison starts with the outcome you want, not with the number of menus. Some people want a connection that is easy to select and enable. Others need traffic to follow a set of domain, IP, or fallback rules. Still others temporarily want all traffic handled by one selected route while diagnosing a rule or connection problem. These are different tasks, so evaluate each app against the behavior you actually need.

In Shadowrocket, Global Routing provides distinct ways to handle traffic. Proxy sends traffic through the selected proxy behavior; Direct sends it directly; Config follows the active configuration’s rules; and Scene uses the selected scene’s settings. For everyday rule-based use, Config is usually the relevant mode. Proxy and Direct are useful for controlled tests, but choosing one globally can bypass the per-domain behavior you expected from a configuration.

Requests follow the rules in the active configuration. A matching rule determines whether a request uses a proxy policy or goes direct; the final rule handles traffic that did not match earlier rules.

Best for: routine use when your existing setup depends on rule-based routing.

Use a proxy-oriented global mode when you deliberately want to test a selected route without relying on individual configuration rules. This is a diagnostic choice, not a substitute for checking the active rules.

Best for: temporary troubleshooting or a controlled all-proxy test.

Use Direct to check whether a destination works without the selected proxy route. If a request succeeds in Direct but fails in Config, inspect the matching rule and its policy rather than changing unrelated settings.

Best for: isolating whether a problem depends on proxy routing.

Rules also require a little operational care. In a configuration, rules are evaluated in order, and a broad rule placed too early can capture requests intended for a more specific rule. A final fallback such as FINAL determines what happens when earlier rules do not match. If a destination behaves unexpectedly, inspect the rule that should match it, the policy named by that rule, and the fallback. Do not assume that changing the global mode will repair an incorrect rule order.

Choose by the work you need to do

If your normal workflow depends on several routing rules, prioritize clear configuration management and predictable rule testing. If you rarely need rules, prioritize the simplest repeatable path from selecting an existing connection to confirming that it works.

3. Test the setup before relying on it

A clean test prevents a common mistake: changing the app, subscription, routing mode, and network at the same time, then not knowing which change caused the result. Keep the test narrow. Use the same iPhone and network, leave the subscription unchanged, and test a destination you can reliably access. If your normal setup uses rules, test it in Config rather than judging it only in a global Proxy mode.

Record the baseline

In Home, note the selected connection and current Global Routing mode. Confirm that the connection entries you expect are present. If you already have a working setup, record its current state before editing or importing anything.
Check the config

Open Config and confirm which configuration is selected. If you rely on rules, return to Home and set Global Routing to Config. Avoid replacing a file just to test whether a subscription import works.
Test one request

Turn on the connection, wait for the system VPN status to update, and make a fresh request to a destination relevant to your normal use. Reopen the page or app so an existing connection does not obscure the result.
Isolate failures

If the request fails, test one alternative routing mode only as a diagnostic. Then return to the intended mode and inspect the matching rule, selected policy, and connection state separately.
Keep what works

Change one setting at a time and repeat the same request. Once the intended behavior is confirmed, avoid further edits to unrelated rules or subscription details.

A VPN indicator confirms a tunnel state; it does not show which policy a particular request used. Likewise, a successful connectivity test does not prove that every app or domain follows the route you intend. Check the specific destination and, when available, the relevant connection or request records. This distinction matters when comparing ease of use: a setup is only easy to maintain if you can tell what it is doing when something fails.

4. Compare daily controls and maintenance

For daily use, consider the actions you repeat rather than the settings you may open once. Can you find the selected connection quickly? Can you tell whether the connection is active? Can you identify the current Global Routing mode? Can you refresh your own subscription without accidentally replacing a local configuration? These small checks often matter more than advanced options that rarely affect your routine.

Shadowrocket separates several tasks across Home, Config, Data, and Settings. Home is where you manage existing connections and connection status. Config is for configuration files. Data provides traffic-related information, while Settings contains app preferences and controls such as On Demand. Remember that a screen name and a routing mode may share a label: Config in Global Routing is a mode, whereas Config is also the place to manage files.

For a simple routine: Keep a known working connection selected, use the routing mode your setup requires, and avoid editing rules unless you have a specific reason.
For rule-heavy use: Keep a copy of the working configuration, check rule order, and verify the fallback behavior after edits.
For automatic connection behavior: Review Settings → On Demand separately from Global Routing. On Demand controls when a connection is requested; it does not decide how a request is routed.
For troubleshooting: Record the network, selected connection, routing mode, and test destination. Change one variable at a time so the result remains interpretable.

Subscription compatibility should be judged on a representative test, not just a successful refresh. After importing or updating your own subscription, confirm that the expected entries remain available and that the intended configuration is still active. Then test the routing behavior you depend on. If your setup uses a particular protocol or rule feature, verify that exact use case before making the app your daily choice. A broad claim that a subscription “works” may conceal a missing rule, a different fallback, or a connection entry that was not imported as expected.

Also consider the amount of maintenance you want to own. More hands-on control can be useful when you understand why a rule exists and how to test it. It can also make troubleshooting harder if several settings are changed without notes. A simpler workflow is not automatically less capable; it may simply make fewer decisions part of your daily routine. Choose the balance that matches your experience and the complexity of your existing configuration.

5. Common questions

Can I use the same subscription in a different app?

Possibly, but do not assume that a refresh transfers every setting or rule. Check which subscription format and configuration features your provider supports, then test the entries and routing behavior you actually need. Keep a record of your current working setup before switching.

Does a successful import mean the rules are working?

No. An import can add connection entries without confirming that the active configuration, rule order, and fallback behave as intended. In Shadowrocket, confirm the selected file in Config, choose Config under Global Routing if you want rule-based routing, and test a fresh request.

Why does a page work in Proxy mode but not in Config?

Config follows the active configuration’s rules; Proxy mode tests a different routing behavior. Check which rule should match the destination, whether that rule names the intended policy, and what the final fallback does. Change one item at a time and retry the same destination.

Should I choose the app with the most options?

Not necessarily. Choose the app that supports your required subscription and configuration features and lets you verify the behavior you care about. If you rarely edit rules, a clear everyday workflow may matter more than controls you will not use. If you rely on custom routing, prioritize testability and configuration management.

The practical choice is the one that fits your existing setup and your willingness to maintain it. For Shadowrocket, first confirm that your own subscription and configuration work, then test the routing mode and rules you plan to use every day. Keep the test specific, preserve a known working state, and make the final decision on repeatable behavior—not on an import screen or a feature list alone.