Clash Verge Rev: Subscription Auto-Update Setup

This updates the subscription file, not the application

When a provider changes its nodes, the copy on your computer may still contain the previous configuration. Automatic subscription updates can reduce the need to refresh that copy manually. They cannot renew an expired account or repair a revoked subscription URL.

This guide covers Clash Verge Rev v2.5.2 on Windows 10/11, x64 or ARM64, using the English interface. It is a maintained project, distinct from the discontinued Clash for Windows. Start with an existing Remote profile that you can already update manually. This is not a guide for Local files or Mihomo provider refresh intervals.

Each profile has its own update options. Editing one card does not set the interval for every subscription, and it does not enable application upgrades. Privately record the current interval and auto-update switch before changing anything, so you can restore them later.

Use Edit Info and enter an interval in minutes

Open Profiles and locate the remote subscription you want to change.
Right-click its card and choose Edit Info, not Edit File. The latter edits configuration content rather than its refresh schedule.
Leave the type as Remote. Enter a positive whole number in Update Interval; the unit is minutes.
Enable Allow Auto Update. Leave the URL and unrelated options unchanged, then save.
Open Edit Info again and check both the saved number and the switch. Resolve any error rather than treating a closed dialog as proof of success.

For example, if your provider recommends updating every 24 hours, enter 1440, not 24. This is a conversion example, not a universal interval recommendation. Follow the provider's published refresh policy and request limits; do not repeatedly shorten the interval to one minute just to test it.

Keep security options unchanged: scheduling does not require allowing invalid certificates, resetting a Token, changing the subscription URL, or toggling TUN. The editor may expose the complete subscription address. Hide the entire sensitive URL before sharing a screenshot.

Why do the documentation and the editor use different units?

The two units belong to different inputs. The profile editor stores Update Interval in minutes. A provider's HTTP response header, profile-update-interval, is expressed in hours. Version 2.5.2 multiplies the header value by 60 when it uses that header; an explicitly supplied profile interval takes precedence.

Intended interval	Editor value	Meaning
1 hour	`60`	60 minutes
6 hours	`360`	360 minutes
24 hours	`1440`	1440 minutes
24 in the response header	Converts to `1440`	Do not copy the header number into the editor as minutes

The enabled switch alone is not sufficient: the scheduler also needs a valid positive interval. Do not assume that clearing the field always restores a provider default. If your goal is to stop automatic updates, use the explicit switch instead of relying on a blank field or a special number.

Check real updates, not just the countdown

After saving, click the refresh icon on the profile card once to confirm that a manual download still works. Click the update-time text on the card to switch between the last update and next-update information. A successful manual refresh only proves that particular request worked. To verify the automatic schedule, keep the application running and connected, and observe it over the configured interval.

In v2.5.2, another interval is scheduled after an automatic task finishes. Startup also checks for overdue tasks. This is not an alarm set to a particular time of day, and it cannot run while the computer is off or the application has fully exited. Sleep, request duration and network failures affect what you observe.

The displayed time is not the queue itself: this version calculates the card's next-update time from the recorded update time plus the interval. It does not read the actual remaining queue delay. After changing the interval, an expired countdown or failure label alone does not establish that a download has just failed; compare actual errors, refresh results and timestamp changes.

An unchanged node count does not mean the update failed: the provider may return the same content. Check whether the request succeeded and a new update time was recorded. If needed, review scheduled-update messages in the application logs. Remove URLs, Tokens and node credentials before sharing diagnostic material.

If nothing updates, check the settings before shortening the interval

Reopen the affected profile and confirm that Allow Auto Update is enabled and the interval is positive. Also confirm that the application has not exited. If a manual refresh fails too, a shorter interval usually only repeats the failing request. Use the error to check subscription validity, connectivity and provider status; do not disable certificate verification to silence it.

To undo this interval change, restore the number of minutes and switch state you recorded earlier, save, and check them again. If you previously did not use automatic updates and want to stop them, disable Allow Auto Update and save. There is no need to delete the subscription, clear its configuration directory or reinstall the application.

Disabling the switch removes future automatic scheduling, but do not assume it immediately interrupts a download already in progress. It also does not restore configuration content that an earlier update replaced. Restoring a schedule and restoring an old file are different operations; this guide changes only the scheduling options.

Official sources and version scope

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