Installation

Installation

Grab the latest build from the Releases page. Each asset is a .zip containing a single self-contained executable — no .NET runtime or installer needed.

OS	Download	How to run
Windows 10/11	1clickTransfer-win-x64.zip	Unzip, double-click 1clickTransfer.exe.
Linux (x64)	1clickTransfer-linux-x64.zip	Unzip, then chmod +x 1clickTransfer-linux-x64 && ./1clickTransfer-linux-x64
macOS (Intel)	1clickTransfer-osx-x64.zip	Unzip to get 1clickTransfer.app, then right-click → Open.
macOS (Apple Silicon)	1clickTransfer-osx-arm64.zip	Same as Intel, but the arm64 build.

"Windows protected your PC" (SmartScreen)

The app isn't code-signed (that requires a paid certificate), so Windows SmartScreen shows a warning the first time you run a freshly downloaded build. Click More info → Run anyway. This is expected and only happens once per download.

"cannot be opened because it is from an unidentified developer" (Gatekeeper)

Same reason on macOS — the build isn't notarized/signed with an Apple Developer certificate. Right-click (or Control-click) the .app → Open, then confirm in the dialog that appears. A plain double-click on a freshly downloaded .app will refuse to open; right-click → Open is the way around it, and only needs doing once.

Where the settings file lives

settings.json is created next to the executable — the app is fully portable, so you can run it from a USB drive or any folder without touching the registry or your system.

• macOS: next to 1clickTransfer.app/Contents/MacOS/1clickTransfer (i.e., inside the .app bundle, Contents/MacOS/).
• Linux/macOS fallback: if that folder isn't writable (e.g. the app lives in a read-only location), it falls back to ~/.config/1clicktransfer/settings.json.

See Settings Reference for what's stored there — and note it's never something you should copy between machines with different FTP/SFTP passwords without care, since passwords are encrypted per-machine (see below).

Password storage

• Windows: encrypted with DPAPI, tied to your Windows user account. A settings.json copied to another PC (or another Windows user) won't be able to decrypt the passwords.
• Linux/macOS: obfuscated with a local AES key stored next to the settings file — this is not strong security, just enough to avoid storing raw plaintext. Treat settings.json as sensitive on these platforms.

Multiple installed copies

You can have more than one copy of the app in different folders (e.g. testing two versions side by side) — each copy runs independently. Launching the same executable a second time (same path) won't open a duplicate window; it brings the already-running instance to the front instead. See Watch Mode and Tray for details.

Building from source instead

If you'd rather build it yourself (or run on a platform without a prebuilt release), see Building from Source.