A video resizer is a tool that changes the pixel dimensions — width and height — of a video file while leaving its duration and content otherwise intact. The Video Resizer on Lizely does this entirely in your browser: you pick a local file, enter a maximum width and height, choose Fit to preserve aspect ratio or Stretch to force exact dimensions, and receive a downloadable WebM. The source file never leaves your device because decoding, canvas drawing, and MediaRecorder capture all happen inside the current tab. Output is a real-time re-encode produced at up to 30 frames per second using the browser's built-in VP9 or VP8 WebM configuration, so processing usually takes about as long as the video itself. Unlike a metadata-only dimension change that simply rewrites container fields, this is a true frame-by-frame re-encode: every decoded frame is drawn onto a resized canvas and recorded again, which means quality, bitrate, frame timing, audio layout, and file size can all shift from the source.
What "Video Resizer" Means in Plain English
A video resizer, in the strictest sense, is any program that alters the spatial resolution of a video. Resolution is the count of pixels along the width and the height — for example 1920×1080, 1080×1920, or 1080×1080. Changing that count is what separates "resizing" from related operations like trimming (cutting duration), cropping (removing edges), or compressing (reducing bitrate at the same dimensions).
The Video Resizer tool focuses on this single operation. It accepts short MP4, WebM, MOV, M4V, or Ogg files and produces a WebM output sized to whatever whole-number dimensions you request, up to 1920 pixels on a side. There is no timeline editor, no effects panel, no transcoding queue — just a controlled path from one local file to a smaller or differently-shaped local file.
That is the short answer to "video resizer meaning": it is a focused utility that re-encodes a video so its pixel grid matches a new target, and the version you are reading about does so without ever sending the source to a server.
Two Ways Resizing Works: Fit vs Stretch
Most people who search for video resizer meaning want to know what choices the tool actually offers. Video Resizer exposes two geometry modes, and the difference between them is the single most important decision you will make.
Fit treats the width and height you enter as a bounding box. The tool applies the smaller of the two requested dimension scales to the source, so the output fits inside the box while preserving the source aspect ratio. Nothing is cropped.
Stretch uses the requested width and height independently. The output frame is exactly the size you typed, even if that means stretching a 16:9 source into a 1:1 square or a 9:16 portrait. Stretch is the right choice when the destination requires a specific pixel grid and you are willing to accept distortion.
| Mode | Treats dimensions as | Aspect ratio | Can distort | Crops source |
|---|---|---|---|---|
| Fit | A bounding box | Preserved | No | No |
| Stretch | Exact pixel target | Ignored | Yes | No |
Neither mode upsamples detail. If you ask for dimensions larger than the source, the encoded video is not made sharper; the same pixels are simply placed into a bigger frame. For real upscaling you need a separate super-resolution tool or a desktop encoder.
What the Output Looks Like
The result of using Video Resizer is always a single WebM file downloaded directly from your browser tab. WebM is the chosen container because modern browsers ship with native VP8 and VP9 decoders, which lets the tool avoid bundling a large media dependency or routing files to a server-side encoder. The MDN reference for HTMLCanvasElement.captureStream and the MDN reference for MediaRecorder document the exact browser APIs that produce this file.
Because the output is a real-time re-encode rather than a metadata patch, several properties can drift from the source. Visual quality and bitrate are chosen by MediaRecorder's supported VP9 or VP8 configuration, not copied from the source. Frame timing is set by the canvas capture rate, capped at 30 fps. Audio is taken from whatever audio tracks the browser exposes on the source and re-encoded into the WebM. File size, color metadata, and track layout can differ noticeably.
The tool also writes a finite duration into the WebM through an audited Matroska duration patcher. Without that step, MediaRecorder output sometimes reports an open-ended duration, which confuses players and editors. Patching the duration makes the file behave like a normal, finished clip.
How to Resize a Video Locally with Video Resizer
This is the practical side of "video resizer meaning" — what you actually click. Open the Video Resizer tool and follow these steps:
- Choose one supported local video (MP4, WebM, MOV, M4V, or Ogg). Wait for the browser to finish loading the file's metadata before touching any other control.
- Enter a maximum width and a maximum height as whole numbers between 2 and 1920. Pick Fit to preserve aspect ratio inside that bounding box, or Stretch to produce exactly those dimensions.
- Select Resize video. Keep the current tab open and in the foreground while the browser decodes frames, draws them to a resized canvas, captures that canvas at up to 30 fps, and records the result through MediaRecorder.
- When encoding finishes, the tool exposes a download link for the WebM. Save the file locally and verify the dimensions in any player before reusing it.
The tab must stay open because the entire pipeline runs in JavaScript on the page. Closing or backgrounding the tab mid-encode will interrupt the recording and the file will not finish. Processing normally takes about as long as the source video itself, since this is a real-time re-encode rather than a faster-than-realtime batch job.
Hard Limits and What the Tool Will Refuse
Every constraint below comes directly from the verified product behavior. Exceeding any of them produces a visible error rather than a misleading download.
| Parameter | Limit |
|---|---|
| Output width and height | 2–1920 pixels each, whole numbers, rounded down to even values |
| Source file size | Up to 500 MiB |
| Source duration | Up to 5 minutes |
| Source per-side resolution | Up to 4096 pixels |
| Source total area | Up to 3840 × 2160 pixels |
| Output frame rate | Capped at 30 fps |
| Output container | WebM (VP9 or VP8) |
Two subtleties are worth highlighting. First, odd pixel values are reduced by one: if you type 721, the encoder receives 720. Even dimensions are more reliable with common browser video encoders, which is why the tool rounds down safely rather than rejecting the input outright. Second, the source limit applies to raw file size and duration together with resolution, not just resolution in isolation — for example, a 1080-pixel video that runs an hour is not allowed, even though each side stays within the per-side cap.
When Video Resizer Is the Right Tool vs a Desktop Encoder
Video Resizer is built for a narrow job and does it well: a quick, private, browser-only resize of a short clip. It is a good fit when you want to downscale a phone recording before sharing it somewhere with a size cap, when you need a specific pixel grid for a social platform and are willing to use Fit or Stretch to hit it, when you would rather not upload a personal or work file to a remote server, or when the clip is short enough that real-time re-encoding is acceptable.
It is the wrong tool when you need frame-accurate delivery, color-managed mastering, or a specific bitrate; when the output format must be MP4, MOV, or another non-WebM container; when the source is longer than five minutes or larger than 500 MiB; or when you need to preserve multiple audio tracks, subtitles, or chapter markers — Video Resizer does not promise any of those. For any of those cases, a dedicated desktop encoder such as HandBrake, FFmpeg, or a Resolve export is the appropriate workflow. The browser tool is not a replacement for professional finishing.
Privacy and Processing Location
A common worry when people hear "online video resizer" is whether the file is uploaded. The verified answer for this tool is no: decoding, canvas resizing, MediaRecorder capture, and download URL generation all happen in the current browser tab. Nothing is sent to a remote server, and the source can be a file you have only on your local disk. The MDN documentation for the underlying canvas captureStream and MediaRecorder Web APIs describes the client-side architecture that makes this possible.
This local-first design has practical consequences. You can resize sensitive material — internal screen recordings, draft footage, anything not yet public — without trusting a third party's data retention policy. You do, of course, need to trust your own browser, and you should still confirm the dimensions and visual quality of the output before treating it as final. The related guide Is an Online Video Resizer Safe? What Really Happens walks through the same pipeline in more detail.
You should still respect copyright and ownership. The product contract reminds users to resize only media they own or have the right to edit, and to avoid bypassing DRM or other access controls on protected content.
If you're weighing options, Video to Audio Converter Alternative: Local Browser Extraction covers this in detail.