Presets
Presets allow you to define and reuse common sets of options for creating or modifying torrents. This is particularly useful if you frequently create torrents for specific trackers with consistent settings.
Configuration
Learn about the presets.yaml file structure
Options
Available preset configuration options
Usage
How to use presets in commands
Overrides
Command-line flag precedence
Configuration File (presets.yaml
)
Presets are defined in a YAML file named presets.yaml
. mkbrr
searches for this file in the following locations, using the first one it finds:
- Path specified by the
--preset-file
flag (if used) - The current working directory (
./presets.yaml
) ~/.config/mkbrr/presets.yaml
(or equivalent user config directory)~/.mkbrr/presets.yaml
(legacy location)
Structure
The presets.yaml
file follows this structure:
Available Options
The following options can be used within the default
section or any specific preset:
List of announce URLs. The first one is used as the primary tracker.
Whether the torrent should be private.
Source tag string.
Torrent comment string.
List of announce URLs. The first one is used as the primary tracker.
Whether the torrent should be private.
Source tag string.
Torrent comment string.
Piece size exponent (e.g., 18
for 256 KiB).
Maximum piece size exponent for automatic calculation.
List of glob patterns to exclude files.
List of glob patterns to include files (takes precedence over exclude).
Whether to prevent adding the tracker domain prefix to the output filename.
List of web seed URLs.
Manually specify the number of concurrent goroutines used for hashing.
Experimenting with different values might yield better performance than the default automatic setting.
Whether to randomize the torrent’s info hash by adding a unique, random key to the info dictionary.
Useful for cross-seeding identical content on trackers that reject duplicate info hashes.
Whether to omit creation date.
Whether to omit creator string.
You can find the formal JSON schema for validation here.
Using Presets
Specify the preset name using the -P
(or --preset
) flag with the create
or modify
commands:
Overriding Presets
Command-line flags take precedence over preset settings. Most flags completely override their preset counterparts, but filtering options have special behavior:
- Filtering patterns are additive: Command-line patterns combine with preset patterns
Standard command-line flags (like --private
or --source
) completely override their preset values, while filtering patterns combine additively.
For complete details on filter processing and pattern syntax, see the Filtering documentation.
Was this page helpful?