Batch mode is ideal for creating multiple torrents in one go.
Configuration File (batch.yaml)
Batch operations are defined in a YAML file, typically named batch.yaml.
Configuration Structure
- Movies Example
- TV Shows Example
- Mixed Content
Configuration Options
Required Fields
- version: Must be
1 - jobs: List of torrent creation tasks
- output: Path for the
.torrentfile - path: Source file/directory path
Optional Settings
- trackers: Announce URLs list
- webseeds: Web seed URLs list
- private: Set to
trueorfalse. The default istrue. - piece_length: Piece size exponent
- max_piece_length: Maximum piece size exponent
- target_piece_count: Target number of pieces (mutually exclusive with piece_length)
Additional Optional Settings
Additional Optional Settings
- comment: Torrent comment string
- source: Source tag string. If you do not set it, mkbrr uses the default source of the first tracker, when that tracker has one. Set
source: ""to add no source. - entropy: Set
trueto randomize info hash for cross-seeding - no_date: Set
trueto omit creation date - no_creator: Set
trueto omit the creator string - skip_prefix: Set
trueto prevent adding tracker domain prefix to output filename - fail_on_season_warning: Set
trueto exit with error on missing episodes in season packs - exclude_patterns: Glob patterns to exclude files
- include_patterns: Glob patterns to include files
Failed jobs
When a job fails, mkbrr continues with the other jobs. The torrents from the jobs that succeed stay on disk. After all jobs run, mkbrr exits with a non-zero code and printsN of M batch jobs failed. A script can use this exit code to find a missing torrent.
With --quiet, mkbrr prints each failed job to stderr as Failed: <output>: <error>. Without --quiet, use --verbose to see the error for each job.
Command-line flags
You cannot provide a source path argument directly to
mkbrr create when using the -b flag. All source paths must be defined within the batch file jobs.
