Skip to content
Tools
Mass Editor

Mass Editor

Mass Editor changes source URLs for multiple Streams, Movies, or Episodes with one regular-expression replacement. Preview the changes, then confirm them.

Warning

Bulk Changes Are Immediate: Create a current database backup and test the expression on one Category before applying it globally.

Run the Mass Editor

1. Preview With Dry Run

  1. Open Tools → Mass Editor.
  2. Select Stream, Movie, Episode, or All types. Choose one type to limit the affected media.
  3. Enter the regular expression and replacement value.
  4. Optionally select a Category. When selected, only records in that Category are evaluated.
  5. Run Dry run.

Review every proposed old and new source. A dry run does not modify the database.

The result page displays at most the first 1,000 changed source values for review. Confirmation still applies the complete server-side preview, so narrow a large change by media type and Category when practical.

2. Apply the Preview

Select Confirm and Apply only when the preview is correct. If the pattern, replacement, type, Category, or matching records change, run another dry run; do not rely on an older preview.

Each preview can be applied once and expires after 15 minutes. Changes to form fields, matching sources, or Categories require a new dry run.

Regular-Expression Syntax

Use RE2 regular expressions. Lookbehind and backreferences within the pattern are not supported.

Replacement strings support:

  • $1 or ${1} for a numbered capture group;
  • ${name} for a named capture group;
  • $$ for a literal dollar sign.

Use braces when text follows a capture group: ${1}suffix means group 1 followed by suffix, while $1suffix may be interpreted as a different capture name.

Pattern and replacement fields are limited to 4,096 characters. Each Stream source URL is evaluated independently. A Movie or Episode source cannot exceed its 1,024-character storage limit, and any individual source is rejected if replacement processing would exceed the 1 MiB server safety limit.

Safety Recommendations

  • anchor patterns when only a URL prefix or suffix should change;
  • escape literal dots and query-string characters;
  • test on one Category before applying globally;
  • keep a current database backup;
  • verify a sample of changed media immediately after applying;
  • avoid broad patterns such as .* unless replacing the entire source is intentional.

Example: replace only the host while preserving the path.

Pattern:     ^https://old\.example\.com/
Replacement: https://new.example.com/

Example: preserve the path with a capture group.

Pattern:     ^https://old\.example\.com/(.*)$
Replacement: https://new.example.com/${1}