Syncthing Tray

Syncthing Tray provides a tray icon and further platform integrations for Syncthing. Check out the website for an overview and screenshots.

The following integrations are provided:

• Tray application
• Context menu extension for the Dolphin file manager
• Plasmoid for KDE Plasma
• Command-line interface
• Android app (still experimental)
• Qt-ish C++ library

---

This document is the main documentation of Syncthing Tray. It is available on the Syncthing Tray website and on GitHub. If you are not already familiar with Syncthing itself, you should also have a look at the Syncthing documentation as this document only covers Syncthing Tray.

Check out the official forum thread for discussions and announcements of new features.

Issues can be created on GitHub but please check the documentation on known bugs and workarounds before.

Syncthing Tray works with Syncthing v2. It also very likely still works with Syncthing v1 (and even v0) but this is not regularly tested anymore. Syncthing Tray is maintained, and updates will be made to support future Syncthing versions as needed.

Supported platforms

Official binaries are provided for Windows (for i686, x86_64 and aarch64), GNU/Linux (for x86_64) and Android (for x86_64 and aarch64). They can be downloaded from the website and the release section on GitHub. However, this is only a fraction of the available downloads. I also provide further repositories for some GNU/Linux distributions. There are also binaries/repositories provided by other distributors. For a list of links, check out the "Download" section of this document.

Syncthing Tray is known to work under:

• Windows 10 and 11
• KDE Plasma
• Openbox using lxqt/LXDE or using Tint2
• GTK-centered desktops such as Cinnamon, GNOME and Xfce (with caveats, see remarks below)
• COSMIC (only simple tray menu works, see remarks below)
• Awesome
• i3
• macOS
• Deepin Desktop Environment
• Sway/Swaybar/Waybar (with caveats, see remarks below)
• Android (still experimental, see Android-specific documentation)

This does not mean Syncthing Tray is actively tested on all of these platforms or desktop environments.

For Plasma 5 and 6, in addition to the Qt Widgets based version, there is also a "native" Plasmoid. Note that the latest version of the Plasmoid generally also requires the latest version of Plasma 5 or 6 as no testing on earlier versions is done. Use the Qt Widgets version on other Plasma versions. Check out the "Configuring Plasmoid" section for further details.

On GTK-centered desktops, have a look at the Arch Wiki for how to achieve a more native look and feel. Under GNOME, one needs to install an extension for tray icon support (unless your distribution already provides such an extension by default).

Limitations of your system tray might affect Syncthing Tray. For instance, when using the mentioned GNOME extension the Syncthing Tray UI shown in the screenshots is only accessible by double-clicking the icon. If your system tray, like on COSMIC, is unable to show the Syncthing Tray UI, you can still use Syncthing Tray for the tray icon and basic functionality accessible via the menu.

Note that under Wayland-based desktops there will be positioning issues. However, the Plasmoid is not affected by this.

The documentation on known bugs and workarounds contains further information and workarounds for certain platform-specific issues, such as the positioning issues under Wayland.

Features

• Provides quick access to the most used features but does not intend to replace the official web-based UI
  • Check state of folders and devices
  • Check current traffic statistics
  • Display further details about folders and devices, such as last file, last scan, items out of sync, etc.
  • Display ongoing downloads
  • Display Syncthing log
  • Trigger a re-scan of a specific folder or all folders
  • Open a folder with the default file browser
  • Pause/resume a specific device or all devices
  • Pause/resume a specific folder
  • View recent history of changes (done locally and remotely)
• Shows "desktop" notifications
  • The events for which to show notifications can be configured
  • Uses Qt's notification support or a D-Bus notification daemon directly
• Provides a wizard for a quick setup
• Allows monitoring the status of the Syncthing systemd unit and starting and stopping it (see section "Configuring systemd integration")
• Provides an option to add the tray to the applications launched when the desktop environment starts
• Can launch Syncthing automatically on startup and display stdout/stderr (useful under Windows)
• Browsing the global file tree and selecting items to add to ignore patterns.
• Provides quick access to the official web-based UI
  • Can be opened as regular browser tab
  • Can be opened in a dedicated window using either
    • Qt WebEngine/WebKit
    • the "app mode" of a Chromium-based browser (e.g. Chrome and Edge)
• Allows switching quickly between multiple Syncthing instances
• Also features a simple command line utility syncthingctl
  • Check status
  • Trigger rescan/pause/resume/restart
  • Wait for idle
  • View and modify raw configuration
  • Supports Bash completion, even for folder and device names
• Also bundles a KIO plugin which shows the status of a Syncthing folder and allows to trigger Syncthing actions in the Dolphin file manager
  • Rescan selected items
  • Rescan entire Syncthing folder
  • Pause/resume Syncthing folder
  • See also the screenshots
• Allows building Syncthing as a library to run it in the same process as the tray/GUI
• English and German localization

Does this launch or bundle Syncthing itself? What about my existing Syncthing installation?

Syncthing Tray does not launch Syncthing itself by default. There should be no interference with your existing Syncthing installation. You might consider different configurations:

• If you're happy with how Syncthing is started on your system, just tell Syncthing Tray to connect to your currently running Syncthing instance in the settings.
  • When starting Syncthing via systemd it is recommended to enable the systemd integration in the settings (see section "Configuring systemd integration").
  • When starting Syncthing by other means (e.g. as Windows service) there are no further integrations provided. Hence, Syncthing Tray cannot know whether Syncthing is expected to be running or not. It will therefore unconditionally attempt to connect with Syncthing continuously as-per the configurable re-connect interval. It will also unconditionally notify when disconnecting from Syncthing if this kind of notification is enabled (so it makes perhaps most sense to disable it).
• If you would like Syncthing Tray to take care of starting Syncthing for you, you can use the Syncthing launcher available in the settings. Note that this is not supported when using the Plasmoid.
  • The Linux and Windows builds provided in the release section on GitHub come with a built-in version of Syncthing which you can consider to use. Note that the built-in version of Syncthing will only be updated when you update Syncthing Tray (either manually or via its updater). The update feature of Syncthing itself is not available this way.
  • In any case you can simply point the launcher to the binary of Syncthing which you have to download/install separately. This way, Syncthing can be (but also has to be) updated independently of Syncthing Tray, e.g. using Syncthing's own update feature.
  • Check out the "Configuring the built-in launcher" section for further details.
• It is also possible to let Syncthing Tray connect to a Syncthing instance running on a different machine.

Note that the experimental UI tailored for mobile devices is more limited. Currently, it can only start a built-in version of Syncthing or connect to an externally started Syncthing instance. It will set a custom config/data directory for Syncthing so any Syncthing instance launched via the mobile UI will not interfere with existing setups.

Installation and deinstallation

Check out the website for obtaining the executable or package. This documentation also lists more options and instructions for building from sources.

If you are using a package manager, you should follow its usual workflow.

Otherwise, you have to extract the archive and launch the contained executable. Especially on Windows, please read the notes on the website before filing any issues. To uninstall, delete the executable again.

Notifications about updates can be enabled in the settings which also allow upgrading to a new version if available. This simply replaces the executable at it