RepurposeThis
Documentation

Everything you need to run a batch.

Installation, activation, the three workspaces, presets, reports and the errors worth knowing about. Short enough to read in one sitting.

Install and activate

  1. Download the installer from the download page and run it. Windows 10/11 64-bit is the shipped build; macOS and Linux builds are sent on request.
  2. Open RepurposeThis. The activation screen appears before any workspace, with a machine ID at the bottom.
  3. Copy the machine ID and send it to us on Telegram together with your platform.
  4. Paste the RT1.… key you receive and press Activate. The check is a signature verification on your CPU; nothing is uploaded and the app works with the network off.

If a stored key stops validating you will see why on the same screen: expired or other-machine. Moving to a new computer means sending the new ID, not buying again.

The three workspaces

WorkspaceWhat it is forTypical use
Video RepurposerVideo sources, full effect stack, copies per sourceOne clip into a week of posts
Image UniquifierPhoto batches, EXIF rewrite, format conversionA folder of stills into unique uploads
Preset MakerBuild, save, edit, import and export effect stacksLocking a look you reuse every week

Two more screens sit behind them: History (every run, its preset and its median distance) and Effects Reference (the table from the effects page, offline). Settings holds the output folder, language, theme and defaults.

Running a batch

  1. Drag files or a folder onto the drop zone, or press Ctrl/Cmd + O.
  2. Set copies per source. The queue shows the total before you start; 2 sources × 240 copies is 480 outputs.
  3. Choose a preset. Each source can use a different one, and each can have its own copy count.
  4. Pick the output folder. Keep it off the system drive if the batch is large.
  5. Press Run. Esc cancels; finished copies are kept, partial files are named so you can delete them.
Encoder choice. The app prefers the hardware encoder available on the machine (NVENC, AMF, VideoToolbox) and retries on x264 if a source is rejected. On hybrid-graphics laptops, forcing the discrete GPU in the OS settings avoids most fallbacks.

Presets and ranges

A preset stores a range per effect, not a single value. When you leave film noise at 4–12, copy one might get 5, copy two 11. That is the mechanism that makes 240 copies of the same source different from each other.

  • Load one of the ten built-in presets as a starting point.
  • Enable a few effects; keep ranges narrow enough that the output still looks intentional.
  • Save the stack with a name you will recognise in History.
  • Export it as .rt-preset.json to move it to another machine, or to keep a backup.

If a preset produces weak results, do not add every effect. Open the Fingerprint Lab, measure the suspects one at a time, and widen the two or three that actually moved the hash on your footage.

Reports and contact sheets

Each run ends with a uniqueness report: a dHash distance per copy and the median for the batch. Higher means further from the source. Low values are a warning about the preset, not a failure of the render.

Contact sheets build a grid montage of outputs with configurable columns and optional filename labels. Use them to check framing, artefacts and watermarks across dozens of copies at once instead of opening files one by one.

Images

The Image Uniquifier applies the 13 transforms, strips the source metadata, then writes a fresh camera EXIF block. Output format can follow the input or be forced to JPG, PNG, WebP or TIFF, with an optional quality or compression reduction per format.

Because EXIF is rewritten per file, a folder of images leaves as a folder of plausible camera exports rather than a folder of screenshots with identical timestamps.

Shortcuts

KeyAction
EscCancel the running batch
?Shortcut overlay
1 – 7Switch workspace
Ctrl / Cmd + OBrowse for sources

Troubleshooting

“Encoder failed (GPU + CPU)”

The source is either corrupt or uses a pixel format the hardware encoder refuses, and the CPU retry hit the same wall. Re-encode the source once with a plain H.264 file, or try a different clip, then rerun. The app already retries automatically; this message means both attempts failed.

Output is huge

Video bitrate and frame rate multiply across copies. Lower the video bitrate range, reduce copies, or trim the tail. A 4K source at 240 copies is a disk-space decision before it is a quality decision.

The report says 1% uniqueness

The preset was too subtle. Enable a geometric effect (pixel shift, zoom, perspective) and increase film noise, then rerun a small batch. Colour-only changes rarely satisfy a perceptual hash.

Videos with no audio fail

They should not: the audio graph is skipped when there is no audio stream. If a specific file still fails, it usually has a malformed container — remux it once and retry.

Windows shows a SmartScreen warning

The installer is not signed with an EV certificate. Check the SHA-256 on the download page against the file you received. The check is also in the licence screen footer.

Your data

Settings, presets and history live in Electron’s userData folder on your machine. Nothing is synced. Uninstalling the app leaves that folder in place unless you remove it; the licence key lives there too, so a reinstall finds it again.

On first launch after upgrading from the older Duplyfi-based build, the legacy duplyfi-data folder is renamed in place so your library survives.


Something not covered? Message us on Telegram — support comes from the person who built the pipeline, not a script.

Read enough? Install it.

Send your machine ID after install and we will issue the key for your licence.