Skip to main content
← Back to Home

Video

6 tools

Play, extract frames and audio from videos

Play, extract audio, capture frames, and split video files — all without uploading heavy files to any server.

Use Cases

  • —Extract audio from a video and save it as MP3
  • —Capture a specific scene as a still image
  • —Split long videos into smaller, manageable segments

Who It's For

Video editors, content creators, and business users handling meeting recordings

Privacy

Video files are never sent to a server — internal meeting recordings and personal videos stay on your device.

Trimming a clip or pulling the audio out of a recording normally starts with installing an editor. Online video converters are the alternative, but uploading a few hundred megabytes is slow, free tiers cap the file size, and a meeting recording or a family video is not something you want to hand over in the first place.

OFFiler's video tools run FFmpeg — the engine behind most video tooling — compiled to WebAssembly and executed inside your browser. Your video is never uploaded; trimming, splitting, compressing, and audio extraction all happen in your device's memory. Below: which tool fits which job, how the processing works and what it requires, the practical size limits, and the questions people ask most.

Choosing the Right Video Tool

Whether you want just one part of a video or a lighter version of the whole thing changes both the tool and how long it takes.

Cutting out the part you need

For a single excerpt, use Video Trim: set the IN and OUT points while watching the preview and it writes that span out as an MP4. To break one file into several pieces, Video Split lets you drop cut points on the timeline and produce up to five clips.

Both copy the existing video stream instead of re-encoding it. Nothing is lost in quality and the job finishes orders of magnitude faster than compression would. The trade-off is that cut points snap to the nearest keyframe, so the boundary can land a few frames off — this is not the tool for frame-exact editing.

Pulling out still images

Video Screenshot lets you play a video and grab whatever frame you like as a PNG. Playback, seeking, speed control (0.25×–2×), and the frame export itself all work in Chrome, Edge, Safari, and Firefox alike.

If you already know the timestamps — 00:15, 01:30, and so on — Extract Frames is faster. Enter several timecodes and it writes out all the matching frames as PNGs at once, which is handy for building documentation or turning a video walkthrough into a written procedure.

Extracting just the audio

Extract Audio pulls only the audio track out of a video, as either MP3 or WAV. MP3 is encoded at a high-quality variable bitrate, which keeps the file small while staying well above what speech needs. WAV is uncompressed 16-bit PCM — nothing is lost, and it is the easier input for transcription services and audio analysis tools.

Typical uses: lifting the audio from a meeting or interview recording before transcribing it, or turning a recorded talk into something you can listen to on the move.

Making the file smaller

When a file will not fit into an email or a chat message, use Video Compress. You choose a compression level and a resolution independently. The level maps to a quality target (CRF): lighter compression keeps more detail, heavier compression makes a smaller file. Pick "keep quality" when you only want to change the resolution with essentially no visible loss.

Resolution options are original, 1080p, 720p, and 480p. If the target is larger than the source, nothing is upscaled — it simply stays at the original size. Vertical phone footage keeps its aspect ratio while being fitted to the chosen height.

Output is H.264 video with AAC audio, so the resulting MP4 plays practically everywhere. Drop in several videos and they are compressed in one run and returned as a ZIP. Do note that compression re-encodes every frame, so it takes far longer than trimming or splitting — cutting the section you need first will save you a lot of waiting.

How Browser-Only Video Processing Works

Running FFmpeg.wasm in the browser

Every tool here loads an engine built by compiling FFmpeg — the standard workhorse of video processing — to WebAssembly. The engine itself is about 30 MB: it is downloaded once, cached afterwards, and reused for the rest of your session. The engine comes over the network, but the video you select does not go anywhere. All processing happens in WebAssembly memory on your device.

The engine is the single-threaded build, so it needs no SharedArrayBuffer and runs wherever WebAssembly does. Current Chrome, Edge, Safari, and Firefox are all verified, Safari on iOS included. It does lean on the device's CPU and memory, so processing can be slow on phones and older machines, and very long videos can exhaust memory.

Memory and processing time

FFmpeg.wasm loads the whole file into WebAssembly memory before it starts, and typically needs two to three times the file size in RAM — so what you can handle depends on your device. Above roughly 150 MB on a phone or 400 MB on a computer, the tools warn you that the run may fail.

Encoding in WebAssembly is also slower than a native app. Compressing a long video end to end can easily take several minutes. Trimming to the section you actually need first, or dropping the resolution to 720p, brings that back to a reasonable wait. Keep the tab open while it runs — the work is happening inside the page, so navigating away cancels it.

Formats and Limits

Input formats
Video files your browser can read, with MP4 recommended
Output formats
MP4 (H.264 + AAC); MP3 and WAV from Extract Audio; PNG from screenshots and frame extraction; ZIP for batch compression
File size
Up to 1 GB per file, but processing needs two to three times that in memory — above 150 MB on mobile or 400 MB on desktop you get a warning
Browser requirements
Current Chrome, Edge, Safari, and Firefox — Safari on iOS included. No SharedArrayBuffer required
First-run download
The processing engine (FFmpeg.wasm, about 30 MB) is fetched once and served from cache afterwards
Cost and sign-up
Free. No account, no sign-in, and no cap on the number of files

Video Tools FAQ

Is my video uploaded anywhere?

No. The video is only read into your device's memory and never sent over the network. The one thing that is downloaded is the processing engine itself, FFmpeg.wasm (about 30 MB) — that is program code, and it has nothing to do with your file.

Do these work in Safari or Firefox?

Yes. The engine is a single-threaded FFmpeg build that needs no SharedArrayBuffer, so it runs in any browser with WebAssembly. Current Chrome, Edge, Safari, and Firefox are verified, including Safari on iPhone. It is CPU-heavy, though, so some devices will be slower than others.

Does trimming or splitting reduce quality?

It does not. Both copy the existing video stream rather than re-encoding it, so the original quality is preserved exactly. In exchange, the cut lands on the nearest keyframe and can be off by a few frames.

The job never finishes, or it fails partway.

Almost always memory. Processing needs two to three times the file size in RAM, so larger videos fail more easily. Trim down to the part you need first, drop the resolution to 720p or 480p, and close other tabs. A computer is considerably more reliable than a phone here.

How much smaller will my video get?

It depends on the source bitrate and the settings you choose. High-bitrate phone footage processed at 720p with medium compression usually drops a great deal. A video that was already compressed for streaming will not shrink nearly as much. Lowering the resolution tends to give the most visible win.

Can I get the audio as an MP3?

Yes — Extract Audio offers MP3 or WAV. Choose uncompressed WAV when the file is going into transcription or analysis, and MP3 when you just want something small to listen to or share.

Can I process several videos at once?

Video Compress accepts multiple files and returns them as a ZIP. Trimming and splitting are per-file, since the cut points differ for every video.

Will the exported MP4 play everywhere?

Compression writes H.264 video with AAC audio, which plays on computers, phones, and the major video platforms. Trim and split outputs simply inherit whatever codec the source used.

Does it work offline?

The app itself is cached as a PWA, so it opens offline. If the processing engine has never been loaded on that device, though, the first download needs a connection — after that it comes from cache.

Video Terms, Briefly

Codec
The scheme used to compress and decompress video or audio. Compression here writes H.264 video and AAC audio.
Stream copy
Copying the video stream instead of re-encoding it. Lossless and fast, but cuts can only land on keyframes.
Keyframe
A frame that can be decoded on its own without reference to its neighbours. It is where a stream copy is allowed to cut.
CRF
The quality target for H.264 encoding. Lower means better quality and a bigger file — the compression levels map onto this value.
Bitrate
How much data is used per second. Higher means better picture and sound but a larger file — the main driver of how much compression can save.
SharedArrayBuffer
A browser feature for sharing memory across threads. Multi-threaded builds of the engine need it; this site uses the single-threaded build, so it is not required.

Related Links