Version 3 (modified by kim, 12 years ago) (diff)


Editing Configuration Files

The GUIs provide access to many but not all Client configuration properties. For some client and all Daemon configuration it is necessary to directly edit the Transmission Configuration File. The location of this file may be found under the [userDocumentation User Documentation] for your system. See the complete list of Configuration Parameters.

Note: Transmission should be shutdown before making changes, otherwise settings may be reverted to it's previous state.

All Flavours except Mac OS X Client

In general Tranmssion uses a JSON formatted file, mainly because of its human readability.
(Consult the JSON for detailed information)


There are three basic types:

Type Values
Boolean true, false
Number Integer or Real depending on context
String surround with (double?) quotes

The settings.json format is:

    "KEY"  :  VALUE,    (for a Boolean or Number)
    "KEY"  :  "VALUE"   (for a string)


    "rpc-enabled": true,
    "peer-port" : 51413,
    "rpc-whitelist": ",192.168.*.*"

Daemon Reload Settings

You can make the daemon reload its settings file by sending it the SIGHUP signal.

$ killall -HUP transmission-daemon

However bear in mind that if you edit settings whilst the daemon is running they may be overwritten. It is preferable to only make changes when the application is not running.

Mac OS X Client Only

Mac OS X has a standardized way of saving user preferences files using XML format. These files are called plist (short for property list) files. Usually there is no need to modify these files directly, since Apple provided a command-line tool to reliably change settings. You do need to restart Transmission before these have effect.

In short:

  • To set a key: defaults write org.m0k.transmission key value
  • To reset a key: defaults delete org.m0k.transmission key