Which files can I start with?

The first workspace accepts common MP4, M4V, MOV, and WebM files. Whether a particular file can be played or transformed depends on the codecs available in the current browser and device.

No. The workspace uses a file you select in the current browser session. It has no account, upload form, cloud drive connection, or server-side media-processing job.

Does this include a full video editor?

No. The focused release deliberately excludes multi-clip editing, effects, captions, filters, remote URLs, GIF conversion, and batch jobs.

Private browser video tools

Prepare an upload-ready video without handing it over.

Inspect a local MP4, MOV, M4V, or WebM file first, then choose a focused change. Aftermath keeps the workflow on this device and only offers operations this browser can support.

Your video stays on this device. No upload, account, or server-side processing job.

See the video facts before you change anything.

Choose one common video file to read browser-observable duration, display dimensions, bytes, container hint, and local playback support. Inspection does not create a copy.

Make a video smaller with a clear quality target.

Choose Smaller, Balanced, or Higher quality—or set a practical file-size limit. The workspace estimates the trade-off locally before a browser-supported encode is attempted.

Keep the right part of a video, without a crowded editor.

Set a start and end for one local clip. Fast trim uses the compatible local path when possible; Exact trim is for frame-oriented boundaries when local re-encoding is supported.

Make an MP4 when the tracks can stay compatible.

Inspect the selected video first. Compatible H.264 video and AAC audio can be remuxed into MP4 without re-encoding; other tracks may need a browser-supported local conversion.

Frame a video for its destination in one deliberate pass.

Choose Original, 16:9, 9:16, 1:1, 4:5, Custom, or an App Store starting point. Then decide whether to crop, fit with a background, or use a blurred background when local encoding is available.

Extract audio from a local video, not from a URL.

Choose one video you own or are allowed to process, select a sensible MP3 bitrate, and use an audio-only local path. Video frames do not need to be decoded for this task.

Prepare an App Store Preview with a compact local checklist.

Choose a recording, select an Apple destination, set a 15–30 second range, preview its framing, and validate measurable output facts. Check Apple’s current documentation before submission.

Browser-local workspace

Open the private video workspace when you are ready.

Choose one local MP4, M4V, MOV, or WebM file. JavaScript activates a browser-native preview and capability check; available conversions depend on the codecs supported by this device.

No upload, account, or server-side media job.

Open private workspace Loads only after you choose to open it.

One focused workspace for common video fixes

Choose a local video, review its observable dimensions, duration, bytes, and playback support, then set one clear goal: make an MP4, reduce its size, trim a clip, change its frame, extract audio, or prepare an App Store Preview. This is not a general timeline editor or a cloud converter.

Smallest valid local change first

The local worker inspects first and can retain compatible tracks before a re-encode. When a codec or container cannot be handled on this browser, Aftermath reports that limitation instead of uploading the file to a fallback service.

Private browser processing

Your video remains in your hands.

Aftermath reads selected video bytes only in the current browser. Unsupported codecs are reported clearly rather than sent to another service. High-resolution conversion can use substantial device battery and processing.

Read the processing boundary

How it works · Privacy & ad choices · Terms of use · Contact