Transmission Remote GUI: every platform points at a releases page that stopped in 2019
🧲 A feature rich cross platform Transmission BitTorrent client. Faster and has more functionality than the built-in web GUI.
At a glance
- What is it?
- transgui is a Pascal front-end that drives a Transmission daemon over its RPC protocol, with four install routes per platform and hand-assembled Windows dependencies. Its newest published release is from October 2019, and the makefile it tells you to use says it was generated in 2011.
- Who is it for?
- Adequate fit: someone already running a Transmission daemon who wants a native desktop client with peer details, per-torrent options and file selection, and who is comfortable assembling a Windows binary by hand. Poor fit: anyone expecting a current download, because the releases page every platform routes to has not been updated since v5.18.0 on 2019-10-12 while the branch itself was pushed on 2026-09-26.
- Can I use it commercially?
- Yes, with conditions. GPL-2.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 50 days ago.
- What is it written in?
- Mainly Pascal, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- transmission-remote-gui/transgui3,473 ★ · +9
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| transmission-remote-gui/transgui | 3.5k | 3.5k |
9 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Every platform routes to a releases page that stopped in October 2019
All three platform sections end up in the same place. Linux precompiled binaries are on the releases page. The macOS disk image is on the release page. The Windows zip and installer are on the same page. What that page holds is old: three visible tags, v5.18.0 published on 2019-10-12, v5.17.0 on 2019-06-25 and v5.16.0 on 2018-12-26. The repository itself is not archived and its last push is dated 2026-09-26, so commits have landed on the branch for close to seven years without producing a new release artifact. That gap is the first thing a reader has to reconcile, because the recommended install route for every operating system is a download rather than a package, and the downloads come from a page whose newest entry predates the branch by that much. Nothing on the page states a build-from-source result or a supported version list, so there is no way to tell from it whether the branch tip is what the installers were made from.
The Makefile says it was generated in 2011, and still targets OS/2 and Amiga
The Linux build section tells you to run `make LAZARUS_DIR=<lazarus_dir>` after a Lazarus project build. The file that command reaches opens with a header saying not to edit it, because it is generated by FPCMake Version 2.0.0 dated 2011-12-25. Its first target is `default: all`. From there the generated content shows its age rather than the project's needs: the target list runs from i386-linux through i386-os2, i386-amiga, i386-beos, i386-atari, i386-netware, i386-wince, m68k-amiga, arm-gba, arm-nds, powerpc-wii, powerpc-morphos, sparc-linux, avr-embedded and watcom variants, alongside the x86_64 and arm entries anyone would want today. Below that sit grouped variables for the BSDs, for the Unixes, for file systems limited to 8.3 format, and for the two platforms that need a command processor to run a batch file. The file also hunts for `pwd.exe` and then `pwd` on the search path and stops with a hard error if neither exists, so even the Windows path expects GNU utils.
Linux needs glibc 2.34, and the Windows zip needs two runtimes installed by hand
The Linux requirement is one line and it is a floor, not a target: precompiled binaries require glibc 2.34 or newer. The Windows requirement is a paragraph of conditionals. If Windows reports `MSVCR120.dll` is missing, install the Microsoft Visual C++ 2013 Redistributable; if `VCRUNTIME140.dll` is missing, install the latest v14 Redistributable. Those are two different runtime families, one from the 2013 generation and one from the v14 generation, and the page closes the note with an instruction not to mix files from different releases or architectures. On top of that sits the TLS problem. The portable archive does not bundle the OpenSSL DLLs, so you either install the OpenSSL 3.x Light package matching your build architecture from a third party, or download the source archive for the tag matching your release and copy the project's own DLLs out of `setup/win/openssl` for 32-bit or `setup/win_amd64/openssl` for 64-bit. Both architecture folders are committed, which is why the second option works at all.
The cheapest install is the one that leaves dependency work to you
The four routes trade size against work, and the page is unusually candid about it. The Windows zip archive is recommended because it is much smaller than the installer, which saves bandwidth, disk space and time. What it saves you there it returns in the dependency note above. The installer carries an extra wizard and bundles the OpenSSL DLLs in every release, is much larger than the zip, and means you do not have to take care of the OpenSSL dependencies at all. The two package manager routes skip the whole question:
choco install transgui
brew install --cask transmission-remote-guiThe macOS route without a package manager is a disk image you mount and drag. On Linux the easy way is a binary you make executable, after which you can create a desktop or menu shortcut to it. Nothing on the page says whether the package manager packages are built from the same commits as the installers, so the version a package manager hands you and the version on the releases page are separate questions.
A transgui.ini beside the binary silently moves every setting out of the user profile
Configuration location is decided by the presence of a file rather than by a flag. If the program finds the transgui.ini file in the same folder as the binary, it stores all configuration and data files in the program's folder instead of the folder in a user profile. Nothing has to be passed on the command line for that to happen, and nothing announces it. Two parameters sit above it. `--home=<home_dir>` specifies a home directory for the program, stores all settings there, and takes precedence over portable mode and the default user-profile location. Because different home directories mean different settings stores, that same parameter is also how you run multiple instances of the program. The second parameter is `-hidden`, which starts the program hidden so only the tray icon shows. The two are written in different styles, one with a single dash and one with a double dash, and the page gives no separate section for either. A path to a .torrent file or a magnet link can also be passed as a parameter, in which case the program adds that torrent.
The advanced parameters section opens a code block and shows nothing inside it
The last settings section states that some parameters in the transgui.ini file cannot be modified via the GUI, then names three issue numbers as the place to read more: #924 for File Manager and Shortcuts, #1020 for a user-defined menu marked Windows only, and #1070 for .torrent auto opening. Then it opens a code block and shows nothing inside it. So the parameter names the section refers to are not on the page at all, and neither is their type, default or range. This matters more than it looks, because the transgui.ini file is the same file whose presence switches the program into portable mode. A file that decides where state lives is also the only place to reach settings the interface does not expose, and the page describes that file in two places without ever printing its contents. The one documented setting in it is the empty file itself, which is how portable mode is triggered.
The fixed hotkeys are numbered in filter order, which ties the keymap to the list
Fourteen hotkeys are documented and the heading calls them fixed, so they are not part of what the interface lets you rebind. Eight of them are a number held with Alt, and they run in the exact order of the torrent filters: all torrents, downloading, completed, active, inactive, stopped, error, waiting. The numbering is therefore positional rather than mnemonic. Nothing in the list is a mnemonic, so the mapping has to be memorised, and if the filter list were ever reordered the key attached to each filter would change with it. Two more keys open panes: Alt+S goes to a search box that filters torrents by keywords, with Esc cancelling the filter and clearing the box, and Alt+G, Alt+K, Alt+P and Alt+F move to the general, trackers, peers and files tabs of the info pane. The tree carries a unit called StringToVK.pas, which is where strings get turned into the key codes these shortcuts need, and a form called colsetup alongside it for column setup.
rpc-spec.txt, GeoIP.pas and a form named passwcon sit in the tree unmentioned
The feature list has seven bullets: a native application for Windows, Linux and macOS, a uTorrent-like interface, selecting files to download, choosing file priority, viewing details about connected peers, full information about each torrent, and per-torrent options. The tree holds more than that. There is `rpc-spec.txt`, the specification for the protocol the page says it speaks over, committed next to the code rather than linked. There is GeoIP.pas and ipresolver.pas, both about resolving where a peer is. There is bencode.pas, which is the encoding a .torrent file is written in, and restranslator.pas beside a lang directory, neither of which the page mentions. There is passwcon.pas with its own form file, sitting beside connoptions and daemonoptions, so a credential prompt for a remote daemon is present in the interface without the page ever raising the subject. And there is AGENTS.md, a file for instructions to automated coding agents, committed at the root of a desktop application. Sixty entries sit there in total, fourteen of them form and code pairs, and three of the rest are licensing files rather than code: `LICENSE`, `COPYING.txt` and `COPYING.FPC`, the last named for the compiler it comes from, sitting alongside a recorded license of GPL-2.0.
Editorial conclusion
Adequate fit: someone already running a Transmission daemon who wants a native desktop client with peer details, per-torrent options and file selection, and who is comfortable assembling a Windows binary by hand. Poor fit: anyone expecting a current download, because the releases page every platform routes to has not been updated since v5.18.0 on 2019-10-12 while the branch itself was pushed on 2026-09-26. Four things are worth checking before adopting it. The portable Windows archive ships without the OpenSSL DLLs and names two different Visual C++ runtimes, so read the dependency note before choosing the zip over the installer. Settings location depends on whether a transgui.ini happens to sit next to the binary, and `--home` overrides both that and the user profile. The advanced settings the GUI cannot reach are named only by issue number, and the section that would list them is empty on the page. And the repository ships three license files, GPL-2.0 in the metadata, a COPYING.txt and a COPYING.FPC tied to the compiler. Nothing here was installed or run.
Frequently asked questions
What is Transmission Remote GUI?
A cross-platform front-end that remotely controls a Transmission daemon over its RPC protocol, written in Pascal using the Lazarus RAD toolchain and the Free Pascal compiler. It runs on Windows, Linux and macOS and offers a uTorrent-like interface with file selection, file priority, peer details and per-torrent options.
How do I install Transmission Remote GUI on Linux?
Precompiled binaries are on the releases page and need glibc 2.34 or newer, so download, extract and run the transgui binary. Building it yourself needs Lazarus and the Free Pascal compiler working first, then `lazbuild -B transgui.lpi --lazarusdir=<lazarus_dir>` and `make LAZARUS_DIR=<lazarus_dir>`.
Does the portable Windows build of Transmission Remote GUI support SSL?
Not out of the box. The zip archive does not bundle the OpenSSL DLLs, so you install the OpenSSL 3.x Light package for your architecture, or copy them from the source archive of the tag matching your release, out of setup/win/openssl for 32-bit or setup/win_amd64/openssl for 64-bit. The installer bundles them instead and is much larger.
How do I keep Transmission Remote GUI settings out of my user profile?
Put a transgui.ini file in the same folder as the binary and the program stores all configuration and data files there instead. The `--home=<home_dir>` parameter does the same deliberately and takes precedence over portable mode and the default user-profile location, and separate home directories give separate instances.
Which transgui.ini settings cannot be changed in the interface?
The page names three by issue number only: #924 for File Manager and Shortcuts, #1020 for a user-defined menu on Windows, and #1070 for .torrent auto opening. The code block that would list the parameters opens and stays empty, so their names and defaults are not given.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/transmission-remote-gui-transgui)Star history chart for your README
[](https://hysenlabs.com/projects/transmission-remote-gui-transgui)Was this useful?