Practical guide · files stay on your device

Check tracks first; extract text or re-encode a short clip.

A subtitle track is not the same as burned-in text or speech. The media tool can convert supported timed-text tracks already in a container. Its short-video export is a separate real-time re-encode, not a lossless copy.

Publisher and editorial responsibility: Project Hubbs · Updated

Open media toolsInspect your files for free

No account required. Prepare resources explicitly before local processing. Inspection is free; cleaning and cleaned downloads require a license.

Supported input

  • For subtitle extraction: supported tx3g timed-text tracks in unfragmented MP4 or MOV.
  • For video export: the tested browser-decodable MP4/WebM subset accepted by the tool, up to 25 MiB, 30 seconds and 1920 × 1080.

Key takeaways

  • Inspect first for free. File format and structure—not the extension alone—determine eligible cleaning.
  • Supported embedded timed text as VTT, or a separately selected short WebM re-encode.
  • Encrypted or signed media stay read-only; unsupported or fragmented structures can be refused.

How to do it safely

  1. Choose a supported media file and inspect the local track inventory.
  2. For subtitles, use the offered timed-text extraction and review the generated VTT. No available track means no supported embedded subtitles, not proof that the video has no visible text.
  3. Do not expect transcription, speech recognition or burned-in subtitle removal; those are not implemented.
  4. For a short WebM copy, select the separate video-conversion operation and review its explicit lossy effects before agreeing.
  5. Choose within the offered 250–4000 kbps range. The output is VP8/Opus WebM at up to 1280 × 720, produced in real time.
  6. Use the existing licensed action, then review and download the completed result. Compare visible samples as a limited check, not whole-video or audio equality.

What this workflow produces

  • Supported embedded timed text as VTT, or a separately selected short WebM re-encode.
  • Only the outputs the selected operation actually reports.

What it does not promise

  • Encrypted or signed media stay read-only; unsupported or fragmented structures can be refused.
  • No MP3/FLAC/MKV conversion or audio-from-MP4 feature is implied.
  • Native decode and WebM encoding support depend on the browser; conversion may change frames, timing and quality.

Retained

  • The original file and previous completed results.

Not checked

  • Transcription, OCR, arbitrary subtitle codecs, every unsampled frame or audio equality.
  • Lossless preservation of timing, frames, quality, HDR or every source track.

Understand the evidence

A VTT export checks the supported subtitle conversion. A completed WebM export is an encoded output, not proof that the original streams were preserved.

Processing, comparisons and verification receipts stay local. PixelRinse sends no product-usage events. Payment and legacy license upgrades are separate online actions that never include selected file contents, names, hashes or metadata.

Common questions

More answers

Do matching video samples prove the videos and audio are identical?

No. Comparison checks only five synchronized video samples; unsampled frames and audio remain Not checked.

Technical details and limits

Missing or unsupported tracks are not reported as equal. A separate short-video conversion is a bounded realtime VP8/Opus WebM re-encode that can change frames, timing and quality; it is not a lossless copy. Matching samples do not prove whole-video, audio or byte equality.

Open supported file comparisonsFull answer

How do I know whether my format is supported?

The file support matrix groups formats into classes such as cleaning supported, inspection only and unsupported.

Technical details and limits

After you add a file, PixelRinse also states which class that exact file falls into and why, before anything is cleaned.

File support matrixFull answer

What is the difference between preserving and re-encoding?

Preserve keeps the original image data and removes only supported metadata; Fresh Export re-encodes the image.

Technical details and limits

Re-encoding can change bytes and quality, so it is an explicit opt-in. PixelRinse never switches to it automatically.

File support matrixFull answer

All frequently asked questions

Free inspection. One-time cleaning unlock.

Individual Pro is EUR 99 total, one-time, including applicable tax. No product tax is added on top. Lifetime (perpetual) use of the version you buy, plus 12 months of updates; update expiry does not revoke that access.

Merchant processing fees are covered. External network or issuer fees outside PixelRinse may be additional. Load purchase options on the pricing page to see currently configured methods.

Review pricing and payment options

All guidesHelpSupport