Skip to main content
The mkbrr modify command allows you to update metadata in existing .torrent files without needing access to the original content files. This is useful for mass-updating trackers, source tags, comments, or other metadata.

Arguments

Required command arguments

Flags

Available modification options

Examples

Common usage examples
By default, the original torrent files are preserved. New, modified files are created with a prefix based on the tracker domain (e.g., tracker-domain_original-name.torrent). You can customize the output filename or directory.
The modify command preserves existing metadata, including custom info-dict keys. Only the fields you explicitly change (name, tracker, source, comment, private flag, entropy) are updated.

​
Arguments

​
string[]
required
One or more paths to the .torrent files you want to modify. Glob patterns (like *.torrent) can be used if your shell supports them.

​
Flags

​
Input & Output

​
string[]
Tracker URLs (can be specified multiple times).
​
string
Set the torrent’s internal name.
​
string
Output directory for modified files.
​
string
Custom output filename (without extension).
When modifying multiple torrents, using --output with a fixed filename will cause subsequent files to overwrite the previous ones. Use --output-dir instead for batch modifications to preserve all modified files with unique names.

​
Advanced Input (Presets)

​
string
Use preset from config.
For reusing common settings across torrents. See the Presets documentation for details.
​
string
Preset config file (default ~/.config/mkbrr/presets.yaml).
Set custom path to presets.yaml. See the Presets documentation for details.

​
Torrent Internals

​
boolean
default:true
Make torrent private.
Private flag is enabled by default for tracker compliance. Only disable if you’re creating a public torrent.
​
boolean
default:false
Remove the private flag entirely.
​
boolean
default:false
Randomize the torrent’s info hash by adding or updating a unique, random entropy key in the info dictionary before hashing.
Cross-seeding is the practice of seeding the same content on multiple trackers. Using the entropy flag helps avoid conflicts between trackers.

​
Seeding & Metadata

​
array
Specify web seed URLs. Can be used multiple times.
Web seeds provide an HTTP fallback source for the torrent content, improving availability.
​
string
Specify the source string.
Some trackers require or recommend specific source tags. Check your tracker’s rules.
​
string
Specify a comment.
​
boolean
default:false
Omit the creation date from the torrent metadata.
If omitted, the creation date is updated to the current time during modification.
​
boolean
default:false
Omit the creator string from the torrent metadata.

​
Execution & Output Control

​
boolean
default:false
Be verbose.
​
boolean
default:false
Enable quiet mode, printing only the final torrent file path upon success. Useful for scripts.
​
boolean
default:false
Don’t add tracker domain prefix to output filename.
​
boolean
default:false
Show what would be modified without making changes.

​
Examples

Update the tracker for a single torrent:
Outputs: new-tracker_original.torrent
Make multiple torrents public:
Outputs: modified_file1.torrent, modified_file2.torrent, etc.
By default, the original torrent files are preserved. New, modified files are created with a prefix based on the tracker domain (e.g., tracker-domain_original-name.torrent). You can customize the output filename or directory.
The modify command preserves existing metadata, including custom info-dict keys. Only the fields you explicitly change are updated.