How Do I Change Clash Verge Rev’s Default Test URL?

A latency test URL is not a subscription URL

The milliseconds shown beside a node are a latency result from accessing a test target through that node, not a download-bandwidth measurement. Default Latency Test takes the target’s HTTP(S) URL. Do not enter a subscription link, node password, or proxy-server connection details.

This guide covers the maintained Clash Verge Rev v2.5.7 stable release on Windows 11, for x64 or ARM64, using the English interface. The procedure was checked against the fixed-version source and official material; it was not tested by clicking through the Windows application. The original Clash Verge, Clash for Windows, and other clients are outside its scope.

The app must already open normally and load the current profile and proxy groups. This change affects only the interface’s default test target. It does not require a patch, a reinstall, administrator privileges, or changes to system proxy, TUN, or DNS. It does not rewrite health-check addresses or intervals in your subscription YAML.

Edit Default Latency Test in Miscellaneous

Open Settings in the main Clash Verge Rev window. Find Verge Basic Setting and click Miscellaneous. This entry is not in Verge Advanced Setting.
Find Default Latency Test and record the value actually entered. If the field is empty and only shows the faint placeholder http://cp.cloudflare.com/generate_204, record it as empty. A placeholder is not a manually saved value.
Enter a complete http:// or https:// address that you trust and are allowed to use for connectivity checks. Include the scheme and hostname, not just a domain. Prefer an HTTPS target with a short response and no login requirement; do not include credentials or private parameters.
Leave the other miscellaneous settings unchanged and click Save. Typing alone does not submit the change. If you have not saved and want to abandon the edit, click Cancel.
Wait for the dialog to close normally, then reopen Miscellaneous through the same path and confirm that the field retains the address. If a save error appears, do not assume either complete success or that nothing changed. Keep the error, inspect the actual value, and restore the original value with Save if needed.

If you do not have a reliable replacement target, leave the existing setting alone. There is no need to keep changing it just to obtain a lower number. A correctly formatted address is not necessarily reachable through every node. Captchas, login pages, service outages, and access restrictions can make a target unsuitable for comparing latency.

These checks make real network requests. Do not use a subscription Token, a download link with authorization parameters, or a private administration address. The target receives requests, and related automatic checks may also access it—not just manual clicks. Avoid large downloads or business pages that require a login.

Why a proxy group may still use a different URL

In v2.5.7, the Proxies page does not always take its test target from Miscellaneous. For valid addresses, priority runs from top to bottom in this table. A value from an earlier source takes precedence over the defaults below it.

Priority	Address source	Effect on the default setting
1	The group’s Delay check URL entered in the interface for this profile	The group-specific interface override wins
2	The proxy group’s `testUrl` returned by the core	The group’s own target can still take precedence
3	Default Latency Test in Miscellaneous	Used when neither of the first two sources has a value
4	`http://cp.cloudflare.com/generate_204`	This version’s built-in fallback, not a required replacement or recommendation

The Delay check URL control in the group header’s tools shows or hides the group’s address field. Hiding the field does not clear a previously entered override. This value is saved for that profile and proxy group; it is not a one-use temporary entry.

Since this task changes only the default, first check whether the group already has an override. Do not delete the profile to verify it. Even after clearing an override you entered, the core-provided group URL can remain in use instead of the Miscellaneous default. The website-test card on Home also has its own site targets; this setting does not replace them all.

Run a fresh check on one actual node

After saving, open Proxies, expand an existing group, and pick an actual node to observe—not a nested policy group, DIRECT, or REJECT. First use the priority table to identify which source should supply this group’s target, then trigger a new check. An old latency number does not demonstrate that the new address was used.

Move the pointer to the test control on the node’s right and click Check. If there is already a positive latency value, clicking that value also runs a new check. Use the control on the right, not the whole node card or name row, so you do not change the selected node at the same time. You do not need the group-wide latency-test button to verify this setting.

Observe the result after the check finishes. A lower millisecond value does not establish faster downloads, access to a streaming service, or successful access to your actual destination. Timeout alone does not establish that the node is unusable. Check the test target actually in effect, the current network, and any error the app displays. Do not change subscriptions, proxy mode, and DNS together because of a single failed check.

Reopening the field checks that its value was retained; running a test checks that this attempt produced a result. Neither alone proves that a particular group used the global default. If either of the first two address sources is populated, interpret the result according to that priority instead of repeatedly saving the default URL.

Restore your previous test address

Return to Settings → Verge Basic Setting → Miscellaneous, put the original recorded value back into Default Latency Test, and click Save. If it was empty, clear the field and save. With no higher-priority address in effect, this version uses http://cp.cloudflare.com/generate_204.

If you also edited a group’s Delay check URL, restore that group’s original value separately. Restoring the Miscellaneous default does not undo a group override, and hiding the group field is not a rollback. Do not clear browser storage, delete the entire profile, or reset all settings just to undo one URL change.

Cancel abandons only the current unsaved edits in Miscellaneous; it does not undo a saved value. After restoring the setting, reopen the field and check the same actual node again. If saving still fails, retain the specific error and stop repeatedly retrying. Reinstalling the client is unnecessary for changing this interface setting.

Official sources and version scope

Version numbers, filenames, and interface labels can change. Confirm them in the linked project documentation before making changes.