{"slug":"update-tailscale","title":"Update Tailscale","tags":["tailscale"],"agent_summary":"Last validated: Dec 4, 2025","trigger_phrases":[],"runnable":false,"markdown":"\r\n# Update Tailscale\r\n\r\nLast validated: Dec 4, 2025\r\n\r\nOur team regularly releases updates for the Tailscale client, and we recommend always being on the latest version of the Tailscale client. To explore all the latest features, changes, and fixes, including release versions of the Tailscale client, refer to our [Changelog](https://tailscale.com/changelog#client) page.\r\n\r\nThere are 3 ways to keep your Tailscale client up-to-date:\r\n\r\n- Auto-updates (recommended)\r\n- Manual updates\r\n- MDM-managed updates\r\n\r\n## [Check for updates](https://tailscale.com/docs/features/client/update\\#check-for-updates)\r\n\r\nTo find the version of the Tailscale client installed on every device in your Tailscale network (known as a tailnet), open the [Machines](https://login.tailscale.com/admin/machines) page of the admin console and refer to the **Version** column. A gray arrow indicates that a standard update is available, a red arrow indicates that a security update is available, and no arrow indicates that the device is up-to-date.\r\n\r\n![Devices showing the Tailscale client version.](https://tailscale.com/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fmachines-versions.106f9dc1.png&w=1080&q=75)\r\n\r\nTo display only the devices where an update is available, select the **Version** filter and select [Update available](https://login.tailscale.com/admin/machines?q=version%3Aupdate-available).\r\n\r\n![Devices showing the Tailscale client and filtered by available updates.](https://tailscale.com/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fmachines-versions-update.bd0d6371.png&w=1080&q=75)\r\n\r\n## [Auto-updates](https://tailscale.com/docs/features/client/update\\#auto-updates)\r\n\r\nTailscale can automatically apply client updates as they are released. To apply the update, the same mechanism is used during the initial client installation. For example, if the client was installed using a Linux package manager, that package manager will be used to upgrade the installed package.\r\n\r\nAuto-updates are optional, and individual devices can be opted in or out of them anytime.\r\n\r\nDevices using the iOS, macOS (App Store version), and Android (Google Play Store version) operating systems might not have automatic updates configured by default. We recommend verifying that this setting is enabled in the App Store and Google Play Store to ensure these devices are updated per with your tailnet settings.\r\n\r\nIf you use [system policies](https://tailscale.com/docs/features/tailscale-system-policies#configure-the-auto-update-settings) to enforce your tailnet updates, auto-updates will occur based on the system policies that you set.\r\n\r\nAuto-updates apply even if the client is disconnected from Tailscale.\r\n\r\n### [Configure auto-updates in your tailnet](https://tailscale.com/docs/features/client/update\\#configure-auto-updates-in-your-tailnet)\r\n\r\nYou must be the [Owner, Admin, or IT admin](https://tailscale.com/docs/reference/user-roles) to enable or disable auto-updates for a tailnet.\r\n\r\nTo enable auto-updates for your entire tailnet, open the [Device management](https://login.tailscale.com/admin/settings/device-management) page of the admin console. Under **Auto-update Tailscale**, enable the **Auto-update new devices** toggle.\r\n\r\n![Auto-update enabled in the admin console.](https://tailscale.com/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fauto-update-on.3523f4e5.png&w=1080&q=75)\r\n\r\nChanging the auto-update setting in the admin console will not change the Tailscale client settings for existing devices. The setting only affects new devices. Existing device owners must manually enable or disable auto-updates.\r\n\r\n### [Auto-updates for new tailnets](https://tailscale.com/docs/features/client/update\\#auto-updates-for-new-tailnets)\r\n\r\nAll newly created tailnets have auto-updates enabled by default in the [Device management](https://login.tailscale.com/admin/settings/device-management) page of the admin console. When a new device is added to the tailnet, the Tailscale client will be configured to automatically update by default.\r\n\r\n### [Auto-updates for existing tailnets](https://tailscale.com/docs/features/client/update\\#auto-updates-for-existing-tailnets)\r\n\r\nIf your tailnet was created prior to February 2024, you must manually enable auto-updates in the [Device management](https://login.tailscale.com/admin/settings/device-management) page of the admin console, and for each of the existing devices. When auto-updates are enabled in the admin console, new devices added to your tailnet will be configured to automatically update by default.\r\n\r\n### [Auto-updates for Docker containers](https://tailscale.com/docs/features/client/update\\#auto-updates-for-docker-containers)\r\n\r\n[Docker](https://tailscale.com/docs/features/containers/docker) containers are designed to be immutable, meaning they are not meant to change over time. Therefore, we recommend using the `stable` tag (`image: tailscale/tailscale:stable`) in your Docker [configuration](https://tailscale.com/docs/features/containers/docker#code-examples) to ensure containers are updated to the latest stable version of the Tailscale client every time they are deployed.\r\n\r\nIt is common for Docker to also use the `latest` tag. In the context of Tailscale, the `latest` and `stable` tags accomplish the same thing, however, we recommend that you use the `stable` tag.\r\n\r\nAlthough you can enable auto-updates within the Tailscale container by setting the Tailscale CLI command [`tailscale set --auto-update`](https://tailscale.com/docs/reference/tailscale-cli#set), be aware of the following limitations:\r\n\r\n- Auto-updates inside a container do not persist between restarts. Therefore, you must reissue the command whenever a container is re-deployed or restarted.\r\n- We recommend setting the version to `stable` and not setting the `auto-update` flag to on. This ensures that each time you deploy or restart the container, it will run with our latest stable version of Tailscale.\r\n- If you have both the `auto-update` flag set for the container and your configuration specifies a version such as `tailscale/tailscale:v1.76.0`, the version of the Tailscale client will revert to this version upon re-deploy or restart and then eventually update to the latest stable version.\r\n- Auto-updates inside a container will ignore the tailnet-wide settings for auto-updates.\r\n\r\n### [Enable auto-updates on devices](https://tailscale.com/docs/features/client/update\\#enable-auto-updates-on-devices)\r\n\r\nYou may need to configure auto-update settings for the Tailscale clients on a device if auto-updates were not previously configured or if you need to disable auto-updates for the device.\r\n\r\nHere's how to change auto-update device settings on different platforms:\r\n\r\n[Windows](https://tailscale.com/docs/features/client/update?tab=windows) [macOS](https://tailscale.com/docs/features/client/update?tab=macos) [iOS](https://tailscale.com/docs/features/client/update?tab=ios) [Android](https://tailscale.com/docs/features/client/update?tab=android) [Linux](https://tailscale.com/docs/features/client/update?tab=linux) [Synology](https://tailscale.com/docs/features/client/update?tab=synology)\r\n\r\nSelect the Tailscale tray icon and toggle **Automatically install updates** under the **Preferences** menu.\r\n\r\n### [Auto-updates for devices on multiple tailnets](https://tailscale.com/docs/features/client/update\\#auto-updates-for-devices-on-multiple-tailnets)\r\n\r\nIf a device has automatic updates enabled and belongs to multiple tailnets where the **Auto-update new devices** setting in the admin console varies, the client will be updated when connected to a tailnet with auto-updates enabled.\r\n\r\n### [Auto-update limitations](https://tailscale.com/docs/features/client/update\\#auto-update-limitations)\r\n\r\nAuto-updates are currently not supported on Synology and Linux distributions based on Arch Linux.\r\n\r\nAuto-updates do not happen immediately when a new version of Tailscale is released. We monitor stability and issue reports for several days before enabling a release for auto-updates. It typically takes around a week after a release before your machines start to update, and it can take longer. Important security updates may be applied faster.\r\n\r\nIf machines with auto-updates enabled are not updated several weeks after a release, [contact support](https://tailscale.com/contact/support).\r\n\r\nScheduling of auto-updates is not currently supported. Auto-updates are automatically scheduled around each node's activity to minimize disruption.\r\n\r\n## [Manual updates](https://tailscale.com/docs/features/client/update\\#manual-updates)\r\n\r\nHere's how to manually upgrade on different platforms:\r\n\r\n[Windows](https://tailscale.com/docs/features/client/update?tab=windows) [macOS](https://tailscale.com/docs/features/client/update?tab=macos) [iOS](https://tailscale.com/docs/features/client/update?tab=ios) [Android](https://tailscale.com/docs/features/client/update?tab=android) [Linux](https://tailscale.com/docs/features/client/update?tab=linux) [Tailscale admin console](https://tailscale.com/docs/features/client/update?tab=tailscale+admin+console) [Synology](https://tailscale.com/docs/features/client/update?tab=synology)\r\n\r\nUpgrade Tailscale by downloading our [Windows installer](https://pkgs.tailscale.com/stable/tailscale-setup-full-latest.exe) and running it. This will update your existing installation to the latest version.\r\n\r\nAlternatively, you can update Windows clients by running the [Tailscale CLI](https://tailscale.com/docs/reference/tailscale-cli) command [`tailscale update`](https://tailscale.com/docs/reference/tailscale-cli#update).\r\n\r\n## [MDM-managed updates](https://tailscale.com/docs/features/client/update\\#mdm-managed-updates)\r\n\r\nTo manage the installed version of Tailscale using MDM, refer to your MDM software documentation. You can also configure the installed Tailscale client using [MDM policies](https://tailscale.com/docs/features/tailscale-system-policies#configure-the-auto-update-settings).\r\n\r\n![Project Logo](https://cdn.brandfetch.io/tailscale.com/fallback/lettermark/theme/dark/h/256/w/256/icon?c=1bfwsmEH20zzEfSNTed)\r\n\r\nAsk AI\r\n\r\nreCAPTCHA\r\n\r\nRecaptcha requires verification.\r\n\r\nprotected by **reCAPTCHA**\r\n","html":"

Update Tailscale

\n

Last validated: Dec 4, 2025

\n

Our team regularly releases updates for the Tailscale client, and we recommend always being on the latest version of the Tailscale client. To explore all the latest features, changes, and fixes, including release versions of the Tailscale client, refer to our Changelog page.

\n

There are 3 ways to keep your Tailscale client up-to-date:

\n\n

Check for updates

\n

To find the version of the Tailscale client installed on every device in your Tailscale network (known as a tailnet), open the Machines page of the admin console and refer to the Version column. A gray arrow indicates that a standard update is available, a red arrow indicates that a security update is available, and no arrow indicates that the device is up-to-date.

\n

\"Devices

\n

To display only the devices where an update is available, select the Version filter and select Update available.

\n

\"Devices

\n

Auto-updates

\n

Tailscale can automatically apply client updates as they are released. To apply the update, the same mechanism is used during the initial client installation. For example, if the client was installed using a Linux package manager, that package manager will be used to upgrade the installed package.

\n

Auto-updates are optional, and individual devices can be opted in or out of them anytime.

\n

Devices using the iOS, macOS (App Store version), and Android (Google Play Store version) operating systems might not have automatic updates configured by default. We recommend verifying that this setting is enabled in the App Store and Google Play Store to ensure these devices are updated per with your tailnet settings.

\n

If you use system policies to enforce your tailnet updates, auto-updates will occur based on the system policies that you set.

\n

Auto-updates apply even if the client is disconnected from Tailscale.

\n

Configure auto-updates in your tailnet

\n

You must be the Owner, Admin, or IT admin to enable or disable auto-updates for a tailnet.

\n

To enable auto-updates for your entire tailnet, open the Device management page of the admin console. Under Auto-update Tailscale, enable the Auto-update new devices toggle.

\n

\"Auto-update

\n

Changing the auto-update setting in the admin console will not change the Tailscale client settings for existing devices. The setting only affects new devices. Existing device owners must manually enable or disable auto-updates.

\n

Auto-updates for new tailnets

\n

All newly created tailnets have auto-updates enabled by default in the Device management page of the admin console. When a new device is added to the tailnet, the Tailscale client will be configured to automatically update by default.

\n

Auto-updates for existing tailnets

\n

If your tailnet was created prior to February 2024, you must manually enable auto-updates in the Device management page of the admin console, and for each of the existing devices. When auto-updates are enabled in the admin console, new devices added to your tailnet will be configured to automatically update by default.

\n

Auto-updates for Docker containers

\n

Docker containers are designed to be immutable, meaning they are not meant to change over time. Therefore, we recommend using the stable tag (image: tailscale/tailscale:stable) in your Docker configuration to ensure containers are updated to the latest stable version of the Tailscale client every time they are deployed.

\n

It is common for Docker to also use the latest tag. In the context of Tailscale, the latest and stable tags accomplish the same thing, however, we recommend that you use the stable tag.

\n

Although you can enable auto-updates within the Tailscale container by setting the Tailscale CLI command tailscale set --auto-update, be aware of the following limitations:

\n\n

Enable auto-updates on devices

\n

You may need to configure auto-update settings for the Tailscale clients on a device if auto-updates were not previously configured or if you need to disable auto-updates for the device.

\n

Here's how to change auto-update device settings on different platforms:

\n

Windows macOS iOS Android Linux Synology

\n

Select the Tailscale tray icon and toggle Automatically install updates under the Preferences menu.

\n

Auto-updates for devices on multiple tailnets

\n

If a device has automatic updates enabled and belongs to multiple tailnets where the Auto-update new devices setting in the admin console varies, the client will be updated when connected to a tailnet with auto-updates enabled.

\n

Auto-update limitations

\n

Auto-updates are currently not supported on Synology and Linux distributions based on Arch Linux.

\n

Auto-updates do not happen immediately when a new version of Tailscale is released. We monitor stability and issue reports for several days before enabling a release for auto-updates. It typically takes around a week after a release before your machines start to update, and it can take longer. Important security updates may be applied faster.

\n

If machines with auto-updates enabled are not updated several weeks after a release, contact support.

\n

Scheduling of auto-updates is not currently supported. Auto-updates are automatically scheduled around each node's activity to minimize disruption.

\n

Manual updates

\n

Here's how to manually upgrade on different platforms:

\n

Windows macOS iOS Android Linux Tailscale admin console Synology

\n

Upgrade Tailscale by downloading our Windows installer and running it. This will update your existing installation to the latest version.

\n

Alternatively, you can update Windows clients by running the Tailscale CLI command tailscale update.

\n

MDM-managed updates

\n

To manage the installed version of Tailscale using MDM, refer to your MDM software documentation. You can also configure the installed Tailscale client using MDM policies.

\n

\"Project

\n

Ask AI

\n

reCAPTCHA

\n

Recaptcha requires verification.

\n

protected by reCAPTCHA

\n"}