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:
Structure The presets.yaml file follows this structure:
Optional settings applied to all presets unless explicitly overridden within a specific preset
A map where each key is the preset name (e.g., ptp, public) and the value contains the options for that preset
Available Options The following options can be used within the default section or any specific preset:
Core Options
Piece Settings
File Control
Advanced
List of announce URLs. The first one is used as the primary tracker.
Whether the torrent should be private.
Piece size exponent (e.g., 18 for 256 KiB). Mutually exclusive with target_piece_count.
Target approximate number of pieces (e.g., 600 or 900). Calculates the optimal piece length automatically. Mutually exclusive with piece_length.
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.
Output directory for created torrents.
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.
Exit with error if season pack completeness check detects missing episodes.
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
Example: Combining Preset and Command-line Filters
Command with Additional Filters
Standard command-line flags (like --private or --source) completely override their preset values, while filtering patterns combine additively.
