In one sentence: SyncTrayzor is a free, open-source Windows program that hosts Syncthing for you and wraps it in a tray icon, a built-in browser window, and native autostart — so a tool that's normally controlled through a web dashboard ends up feeling like ordinary desktop software.

It's a shell, not a replacement

It's worth being precise about what SyncTrayzor actually is, because the name sometimes gets confused with Syncthing itself. Syncthing is the file-synchronization engine — the open-source program that connects your devices directly to each other and keeps chosen folders identical between them, without routing your files through a third-party cloud. Syncthing does all of the real work: scanning folders, negotiating connections, encrypting traffic, and resolving conflicts.

SyncTrayzor doesn't touch any of that. What it does is download, launch, and supervise the actual Syncthing binary as a child process, then present it to you through a proper Windows interface instead of a command prompt and a browser tab. Think of it less as "another sync tool" and more as a costume Syncthing wears specifically for Windows users.

What changes once SyncTrayzor is involved

Running Syncthing on its own on Windows works perfectly well from a technical standpoint, but the day-to-day experience has some rough edges: a console window you have to leave open or hide, a web dashboard that lives in whichever browser tab you happened to open it in, and no obvious way to tell at a glance whether anything is actually syncing right now.

SyncTrayzor's job is to sand down exactly those edges:

• It puts a permanent icon in the system tray that changes appearance while files are transferring.
• It opens Syncthing's web dashboard inside its own embedded browser window, so there's no separate tab to lose track of.
• It can launch automatically when you log into Windows, with no manual service setup.
• It shows a small, dismissable popup window with live transfer progress, similar to what you'd expect from a commercial sync client.
• It can pause syncing automatically on networks you've marked as metered, like a phone hotspot.

Where it came from

SyncTrayzor was originally built by developer Antony Male, known on GitHub as canton7, and for years it was the closest thing to a standard answer to "how do I run Syncthing comfortably on Windows." The project was archived in 2025 after development quietly stopped. Rather than the tool simply disappearing, maintainer GermanCoding took it over — with permission from both the original author and Syncthing's lead developer — and released SyncTrayzor v2: rebuilt on .NET Core 8, compatible with Syncthing v2, and shipped with native ARM64 builds for newer Arm-based Windows machines. The history matters here mainly because it explains why a small utility like this has stayed reliable for so long: it didn't survive by accident, it survived because someone with the right permissions chose to keep maintaining it.

Who actually needs this

If you're comfortable running Syncthing from the command line, keeping a browser tab pinned, and managing autostart yourself, you genuinely don't need SyncTrayzor — Syncthing alone does the same syncing either way. SyncTrayzor exists for the much larger group of people who want Syncthing's privacy and pricing (free, peer-to-peer, no cloud middleman) without learning to operate it like infrastructure. That includes people coming from Dropbox or Google Drive who expect a tray icon and a notification when something finishes, people on laptops who need transfers to pause politely when they tether a phone, and anyone who simply doesn't want a terminal window as part of their daily workflow.

Getting started

If this sounds like what you've been missing, the next step is simply downloading the current release and letting it set Syncthing up for you — there's nothing to install separately. See the downloads section for the current x64, ARM64, and portable builds, or the system requirements if you want to confirm your machine is supported first.

Related guides

Yes — Windows 10 and Windows 11 are exactly what SyncTrayzor v2 is built for. The short version: if your PC can run a current version of Windows, it can run SyncTrayzor. The longer version explains a few details worth knowing before you install it.

Supported versions today

SyncTrayzor v2 requires Windows 10 or newer. That's a deliberate change from the original SyncTrayzor, which also supported Windows Vista, 7, and 8. When the project moved to .NET Core 8 and a modernized dependency stack, the maintainer dropped support for those older versions in exchange for a more secure, more actively supported foundation. If you're running Windows 10 or Windows 11, you're squarely in supported territory and don't need to think about this any further.

Choosing the right architecture

SyncTrayzor v2 ships two architecture builds, and picking the right one matters:

• x64 — for the vast majority of desktops and laptops, which use Intel or AMD processors. This is almost certainly the one you want.
• ARM64 — for Arm-based Windows devices, including newer Copilot+ PCs. This build runs natively rather than through x86 emulation, which means better performance and battery life on those machines.

One more architecture detail worth knowing: 32-bit (x86) builds are no longer offered at all in v2. If you're still running a 32-bit install of the original SyncTrayzor v1, you'll need to uninstall it before installing v2, since the two aren't compatible side by side.

Admin rights: not always required

A common assumption is that any Windows installer needs administrator privileges. SyncTrayzor's installer actually supports a current-user install mode, which doesn't require admin rights at all — useful on managed work laptops or shared family computers where you don't have elevated access. If you do have admin rights and prefer a machine-wide install, that option is still available during setup.

What about SmartScreen or antivirus warnings?

Because SyncTrayzor is a small, volunteer-maintained open-source project rather than a large commercial vendor, Windows SmartScreen or your antivirus software may occasionally flag a fresh install with a generic "unrecognized app" warning. This is common for low-volume open-source installers and isn't unique to SyncTrayzor — it happens because the binary hasn't yet built up enough reputation in Microsoft's telemetry, not because anything is wrong with it. You can verify any release against the checksums published on the official GitHub releases page if you want extra reassurance before running it.

Installer vs portable on Windows 10/11

Both build types work identically on either Windows version — the choice between them is about how you want the app to live on your machine, not about compatibility. If you're not sure which to pick, the dedicated guide on installer vs portable walks through the tradeoffs.

Quick compatibility checklist

• Windows 10 (64-bit) or Windows 11 — required
• x64 or ARM64 processor — required (no 32-bit builds in v2)
• Administrator rights — optional, current-user install mode is available
• Internet connection — needed on first run to fetch the Syncthing binary

Related guides

No — SyncTrayzor itself is, and has always been, a Windows-only application. It's built with .NET and a Windows-specific tray/window API, so there's no macOS or Linux build, official or otherwise. The good news is that Syncthing — the actual sync engine underneath — runs natively on both platforms, and each has its own equivalents to fill the role SyncTrayzor plays on Windows.

Why SyncTrayzor doesn't run on Mac or Linux

SyncTrayzor isn't a cross-platform framework like Electron — it's written specifically against Windows APIs for things like the system tray, native notifications, and the embedded Chromium browser window. Porting it to macOS or Linux wouldn't be a small tweak; it would essentially mean rewriting the application against each platform's own UI toolkit. That's a different project, not a missing checkbox in the existing one, which is why no Mac or Linux build has ever existed for it.

What macOS users should use instead

Syncthing publishes its own official macOS app, distributed as syncthing-macos, which adds a menu bar icon, native notifications, and a packaged installer — covering the same basic need SyncTrayzor covers on Windows, but built specifically for macOS rather than ported from it. It's the most straightforward starting point for Mac users who want something more native than running the Syncthing binary from Terminal and keeping a browser tab open.

What Linux users should use instead

On Linux, the most actively maintained option is Syncthing Tray (the Martchus/syncthingtray project), a Qt-based tray application with official binaries for several distributions, plus deeper integration for KDE Plasma and the Dolphin file manager. It isn't made by the same team as SyncTrayzor and isn't a port of it, but it solves a similar problem for Linux desktops: a tray icon, quick access to common actions, and a launcher that avoids leaving a console window open. Most major desktop environments also let you start the plain Syncthing binary automatically via a systemd user service, which covers autostart even without a dedicated tray app.

Mixing platforms in one sync setup

None of this affects whether your devices can sync with each other. Syncthing's protocol doesn't care what's wrapping it — a Windows machine running SyncTrayzor, a Mac running the official Syncthing app, and a Linux desktop running Syncthing Tray (or plain Syncthing) can all be devices in the same sync setup without any compatibility issues. The wrapper is purely a local convenience layer; it has no effect on how folders sync between machines.

If most of your devices are Windows

If your setup is mostly Windows machines with the occasional Mac or Linux box in the mix, it's worth installing SyncTrayzor on every Windows device first, since that's where it adds the most value, and treating the other platforms' native clients as good-enough equivalents rather than trying to find something identical.

Related guides

SyncTrayzor doesn't reimplement file synchronization — it manages, monitors, and re-presents the real Syncthing binary. Understanding that relationship makes a lot of SyncTrayzor's behavior easier to reason about, especially when something looks unusual and you're trying to work out whether the problem is in SyncTrayzor or in Syncthing itself.

It launches and supervises a real Syncthing process

When you start SyncTrayzor, one of the first things it does is locate (or download, on first run) the actual Syncthing executable and start it as a child process, configured to listen only on a local address rather than being exposed to your network directly. From that point on, SyncTrayzor is responsible for the process's lifecycle: starting it, restarting it if it crashes, and shutting it down cleanly when you exit. If you ever look in Windows Task Manager while SyncTrayzor is running, you'll typically see both SyncTrayzor.exe and a separate syncthing.exe process — that second process is the real sync engine doing the actual work.

The dashboard is the same dashboard, just embedded

Syncthing exposes a local web interface for configuration and monitoring, normally reached by opening a browser to an address like 127.0.0.1:8384. SyncTrayzor's main window is, functionally, an embedded Chromium browser (via CEF) pointed at that same local address. You're not looking at a custom-built SyncTrayzor interface — you're looking at the genuine Syncthing web UI, just hosted inside a native window instead of a regular browser tab, with a GUI authentication token handled automatically so you're never prompted to log in manually.

How the tray icon knows what's happening

Syncthing's local API exposes an event stream that reports what's currently happening — connections being established, scans starting and finishing, files being transferred. SyncTrayzor subscribes to that event stream in the background and uses it to drive the tray icon's appearance and the activity popup window. This is why the tray icon can reflect sync activity almost immediately: it isn't polling a dashboard page, it's listening to the same event feed that powers Syncthing's own UI.

Updating the Syncthing binary

Because SyncTrayzor manages the Syncthing binary itself, it's also responsible for keeping it current. New SyncTrayzor releases generally bundle a compatible Syncthing version, and on first run SyncTrayzor will fetch the appropriate binary if one isn't already present. This is part of why SyncTrayzor v2 specifically supports Syncthing v2's protocol changes — the integration layer had to be updated alongside the engine it manages.

What SyncTrayzor adds on top

On top of process management and the embedded dashboard, SyncTrayzor layers a few Windows-specific conveniences that have nothing to do with Syncthing's own code: the metered-network detection that pauses transfers, the autostart-on-login registration, and the drop-box style transfer popup. All of these are SyncTrayzor features built around the data Syncthing's API already provides — they don't require any special cooperation from Syncthing itself.

Why this architecture matters

Wrapping the real binary rather than reimplementing sync logic has a practical upside: SyncTrayzor inherits Syncthing's actual reliability and security model directly, rather than introducing a second codebase that could drift out of sync with it (so to speak). When Syncthing fixes a bug or improves performance, SyncTrayzor users get that improvement the moment the bundled binary updates — no separate fix needs to be written.

Related guides

Both builds run the exact same SyncTrayzor — same features, same version, same behavior once running. The only real difference is how the app lives on your machine, which mostly comes down to where you're installing it and how much control you want over that process.

The installer (SyncTrayzorSetup-x64.exe / -arm64.exe)

This is the right default for most people. It adds a Start Menu shortcut, registers an uninstaller in Windows' standard Apps list, and can check for updates automatically. It supports a current-user install mode, so you don't need administrator rights unless you specifically want a machine-wide install for multiple user accounts. For anyone setting SyncTrayzor up as a permanent part of their Windows setup — which is most people — the installer is simpler to live with long-term.

The portable build (SyncTrayzorPortable-x64.zip / -arm64.zip)

The portable build is just a ZIP archive: unzip it anywhere, run SyncTrayzor.exe, and that's it — no installer runs, nothing is registered in Windows, and nothing is written outside the folder you unzipped it into. That makes it a good fit for a few specific situations:

• USB drives — carry SyncTrayzor with you and run it on whichever PC you plug into, without installing anything on that machine.
• Locked-down or sandboxed environments — machines where you can't run installers at all, but can still execute a standalone .exe.
• Testing a new release — run a portable copy of a newer version side by side with your main installed copy before committing to an upgrade.

What you give up with portable

The portable build doesn't auto-update, doesn't add a Start Menu entry, and won't appear in your installed-apps list for easy removal — deleting the folder is the entire "uninstall" process. If you update by downloading a newer portable ZIP, you'll need to manually copy your data folder across from the old version so your existing Syncthing configuration and device pairings carry over; the installer's update path handles this automatically.

Can you run both at once?

Yes, with one caveat. A portable copy and an installed copy can run side by side for testing purposes, but they shouldn't be pointed at the same Syncthing data folder simultaneously — that can cause configuration conflicts. If you just want to try a portable copy briefly, it's safest to let it create its own separate data folder rather than reusing your main installation's.

Switching between them later

Moving from portable to installed (or the other way around) doesn't require starting over. Your Syncthing configuration, device IDs, and folder pairings live in a data folder that you can copy across, so switching delivery methods later doesn't mean re-pairing every device from scratch.

Related guides

Close to real-time, with a couple of caveats worth understanding. The tray icon is driven directly by Syncthing's own event stream rather than a periodic check, so in most everyday use it changes within a second or two of activity actually starting or stopping.

What drives the icon's state

As covered in the guide on how the Syncthing integration works, SyncTrayzor subscribes to Syncthing's local event API rather than polling the dashboard. When Syncthing reports that a folder has started or stopped syncing, SyncTrayzor updates the tray icon in response to that specific event. That's a meaningfully different (and more accurate) approach than, say, checking a status page every thirty seconds — it's event-driven rather than guess-and-refresh.

Where small delays can show up

Even with an event-driven design, a few situations can introduce a brief lag between something actually happening and the icon reflecting it:

• Scanning vs. syncing. Syncthing periodically rescans folders for changes before it decides anything needs to transfer. A scan can briefly nudge the icon's state even when no actual file transfer follows, which can look like activity for a moment with nothing to show for it.
• Many small files at once. When hundreds of small files change together (a build output folder, for example), the icon will show ongoing activity for the whole batch rather than flickering per file, which is by design but can make a sync look longer-running than the data volume alone would suggest.
• System sleep and wake. Right after a laptop wakes from sleep, there's a brief window where SyncTrayzor and Syncthing are both re-establishing themselves, and the icon may take a moment to reflect the genuinely current state.

What the icon doesn't tell you

The tray icon is intentionally a glance-level indicator — it tells you whether something is happening, not what or how much. For details on exactly which files are transferring and in which direction, the activity popup window (draggable and resizable since v2.1) shows the actual per-transfer breakdown, and the full dashboard inside SyncTrayzor's main window has the complete picture, including per-folder state and any errors.

Should you trust it for anything critical?

For everyday awareness — "is it safe to close my laptop right now" — yes, the icon is reliable enough to act on. For anything where you need certainty, like confirming a large transfer fully completed before disconnecting from a network, it's worth glancing at the dashboard directly rather than relying on the tray icon alone, the same way you'd check a progress bar rather than assume a download finished just because the taskbar icon looks idle.

Related guides

Yes, actively. It's a fair question to ask, since searching for SyncTrayzor turns up an archived repository that hasn't been touched since 2025 — but that's the old project, not the current one. A new maintainer picked it up and has been shipping regular releases ever since.

What happened to the original project

SyncTrayzor was created and maintained for years by developer Antony Male (canton7 on GitHub). In 2025, that original repository was archived and development on it stopped. For a tool this widely used, that's the kind of moment that can genuinely kill a project — users start looking for alternatives, and an unmaintained Windows utility tends to fall out of date with newer Windows releases fairly quickly.

Who maintains it now

That didn't happen here. Maintainer GermanCoding took over the project with explicit permission from both the original author and from Syncthing's own lead developer, and relaunched it as SyncTrayzor v2 — rebuilt on .NET Core 8, with support for Syncthing v2's protocol changes, native ARM64 builds, and a modernized dependency stack. Ownership of the Chocolatey package was also formally transferred to reflect the same change in maintainership, so the install paths people already relied on kept working under the new project.

Recent release activity

Since the v2.0.0 release, updates have continued at a steady pace — translation updates, dependency upgrades, compatibility fixes for newer Syncthing versions, and user-facing improvements like the draggable, resizable activity popup added in v2.1.0. The current stable release as of this writing is v2.1.0. One specific fix worth highlighting: recent releases added a warning that detects when a machine has a mixed v1/v2 install — leftover files from the old version sitting alongside the new one — because that combination is a known cause of crashes, and flagging it proactively is the kind of detail that only shows up in software someone is still actively paying attention to.

How to confirm you're on a current build

If you want to verify your own install rather than take this page's word for it, the most direct way is to compare your version against the official GitHub releases page, which lists every release with its changelog. If you installed via a package manager, running the corresponding update command — winget upgrade GermanCoding.SyncTrayzor, choco upgrade synctrayzor, or scoop update extras/synctrayzor — will also tell you immediately whether a newer version is available.

What this means for new users

If you're deciding whether to adopt SyncTrayzor today, the maintenance history is genuinely reassuring rather than a red flag: a project that survives a maintainer handoff, with the original author's blessing and a clear continuation plan, tends to be more durable than one that's simply never had to face that test yet.

Related guides

Both approaches end with the same Syncthing engine running on your PC — the difference is entirely in how many manual steps stand between "download" and "actually syncing," and what you have to maintain yourself afterward.

Setting up plain Syncthing on Windows

Syncthing distributes itself as a single executable with no installer. A manual setup typically looks like this:

• Download the Windows binary from the official Syncthing site or GitHub releases.
• Extract it somewhere sensible, since there's no install location chosen for you.
• Run it from a command prompt or by double-clicking, which opens a console window and starts a background web server.
• Open a browser manually and navigate to the local address (commonly 127.0.0.1:8384) to reach the dashboard.
• If you want it to start automatically on login, set that up yourself — typically a shortcut in the Startup folder or a scheduled task, since Windows won't do this for you.
• If you want it reachable outside your own machine, configure firewall rules manually.

None of this is hard for someone comfortable with basic Windows administration, but it is entirely manual, and every step is something you're responsible for getting right and keeping working across Windows updates.

Setting up SyncTrayzor

The same end state — Syncthing running, reachable, and synced — looks like this with SyncTrayzor:

• Download one installer (or portable ZIP) matched to your processor architecture.
• Run it. The Syncthing binary is downloaded and managed automatically — there's no separate file to place anywhere.
• The dashboard opens inside SyncTrayzor's own window the first time you launch it — no browser, no address to remember.
• Autostart on login is a checkbox in settings, not a manually created shortcut.
• The tray icon and activity popup give you status without opening anything.

The underlying configuration — device IDs, shared folders, ignore patterns — is identical either way, because it's the same Syncthing engine and the same settings format underneath. SyncTrayzor doesn't change what you're configuring, only how many of the surrounding steps it does for you.

Updating over time

With a manual Syncthing install, keeping the binary current means watching for new releases yourself and replacing the executable when one comes out, then restarting whatever startup mechanism you set up. With SyncTrayzor, binary updates are handled as part of normal app updates — through the installer's update check or your package manager — without you needing to track Syncthing's release cycle separately.

Uninstalling

Removing a manual Syncthing setup means deleting the executable, removing whatever autostart shortcut or scheduled task you created, and clearing out the data folder if you want a clean removal. SyncTrayzor's installer includes a standard Windows uninstaller that handles this for you, and even prompts about whether to remove the Syncthing configuration and database at the same time, rather than leaving you to track down the pieces manually.

Which approach is right for you

If you're setting Syncthing up on a headless server or need precise control over how it's launched, the manual route still makes sense. For a normal Windows desktop or laptop where you just want files to sync reliably in the background, SyncTrayzor removes nearly all of the setup and maintenance overhead without changing what Syncthing is actually doing underneath.

Related guides