To resize a video correctly, open a local browser tool like Video Resizer, set whole-number width and height between 2 and 1920 pixels, then choose Fit to keep the source aspect ratio or Stretch to force exact dimensions, and download the WebM output that is encoded in real time inside your tab. Correct resizing is not just about typing in numbers; it is about matching the resize mode to your content, staying inside the documented limits, and confirming the output dimensions after download. Because every browser re-encode is a true pixel-by-pixel rebuild rather than a metadata tweak, the picture quality, file size, bitrate, and audio layout can all shift from what the source looked like. The safe path is to know the bounds, decide Fit versus Stretch up front, and verify the result before you treat the WebM as final.
Most "wrong" resize outcomes come from three predictable causes: picking the wrong mode for the content, requesting odd pixel counts that the encoder quietly rounds down, or expecting lossless output from a real-time VP9/VP8 re-encode. Once you understand how each mode treats your numbers and where the encoder draws its lines, the rest of the workflow becomes routine.
What "Correctly" Means When Resizing a Video
A correct resize produces a video that matches the dimensions and mode you intended, plays back as a finite-duration WebM, and visually carries the source content without surprise cropping or stretching. Three properties define "correct" in practice and they are worth pinning down before you start.
- The output dimensions match what you chose. Fit must respect the aspect ratio of the source and never crop; Stretch must hit the exact numbers you typed, even if the picture looks intentionally distorted.
- The resize stays inside browser-safe bounds. Whole-number pixel values from 2 to 1920 on each side, with odd numbers automatically decreased by one pixel so the encoder works with codec-safe even sizes.
- The encoder finishes with a playable file. An empty, zero-length, or infinite-duration WebM signals a failed resize, not a successful one, and surfaces as a visible error rather than a misleading download.
If any of those three checks would fail, the resize has not been done correctly yet, regardless of whether the browser produced a file you can save.
Fit or Stretch: Picking the Right Mode
The first decision that determines whether the result looks correct is which mode you select in Video Resizer. Both modes accept the same width and height fields, but they treat those numbers in opposite ways, and mixing them up is the most common reason a finished file looks wrong.
| Mode | Treats the numbers as | Aspect ratio | Can it distort or crop? |
|---|---|---|---|
| Fit | A bounding box (maximum width and height) | Source ratio always preserved | No distortion; no cropping |
| Stretch | Exact output width and height | Ratio is overridden | Yes, picture can be intentionally distorted |
Use Fit when you only care about a maximum size and want the original framing intact, for example, capping a 4K clip so it fits inside 1280x720. Use Stretch when you must match a fixed pixel rectangle, such as delivering a 1080x1080 square to a destination that rejects anything else and you accept that portrait footage will appear widened.
Set the Right Pixel Dimensions
Before clicking Resize, double-check the numbers you typed. The tool accepts integers from 2 to 1920 on each side. Odd values are silently decreased by one pixel because common browser video encoders are more reliable with codec-safe even sizes, so a request for 1281 produces a 1280-wide output. Your source file itself cannot exceed 500 MiB, five minutes of duration, 4096 pixels on any single side, or 3840 x 2160 pixels of total area. Going past any of these limits surfaces as a visible failure instead of a silent partial file.
The encoder then draws decoded frames onto a resized canvas at up to 30 frames per second, which is why processing time tracks playback time rather than running as an instant metadata patch. The output is always a WebM produced by MediaRecorder using a supported VP9 or VP8 configuration, which is the practical reason you cannot ask for an MP4 from this tool.
Resize a Video Correctly Step by Step
Follow this sequence to keep the resize predictable from start to finish.
- Open Video Resizer in a desktop browser tab and confirm it is a local-only environment, because nothing in the steps below requires uploading the source to a server.
- Choose one local video file in MP4, WebM, MOV, M4V, or Ogg format and wait for the browser to finish decoding its metadata. Selecting the file triggers the metadata load, before the size fields do anything.
- Enter your maximum width and maximum height as whole numbers from 2 to 1920 pixels. Remember that odd numbers are rounded down to even codec-safe values automatically.
- Select Fit to preserve the source aspect ratio inside the bounding box, or Stretch to force the exact width and height even if the image becomes distorted.
- Click Resize video and keep the tab open and focused. Encoding happens in real time at roughly 30 frames per second and typically takes about as long as the source video plays.
- When the download becomes available, save the WebM to your device and verify both the file size and the duration before treating the result as final. Empty recorder output and unsupported codecs fail visibly rather than producing a bogus file.
For more guardrails against common slips around this sequence, see our companion Video Resizer Tips and Common Mistakes to Skip checklist.
Verify Your Result After Download
The resize process is not finished just because a file appeared in your Downloads folder. A correctly resized WebM should pass three quick checks before you upload or share it anywhere.
- Duration. Open the file in a browser or a media player; the WebM carries a finite duration written by the audited Matroska duration writer, so a 42-second source should still be a 42-second result rather than an infinite stream or a 1-second stub.
- Pixel dimensions. Confirm the file's actual width and height match the mode you picked. Fit should never widen or distort the source ratio, and Stretch should hit your numbers exactly, after the automatic odd-to-even rounding.
- Audio and visual presence. Listen for the audio track and confirm it stays in sync through the clip. Audio routing uses any browser-exposed track on the source, so silent output or unexpected tracks in the result mirror what your source carried.
Limits That Affect a Correct Resize
Even with the right mode and well-chosen dimensions, certain inputs will not produce a usable output. The Video Resizer limits, all enforced inside your browser tab, are summarized below.
| Constraint | Value | Why it matters for correctness |
|---|---|---|
| Output dimensions | 2 to 1920 px per side, even integers | Outside this range the encoder cannot produce a reliable WebM |
| Maximum source size | 500 MiB | Larger files exhaust browser memory and fail visibly |
| Maximum source duration | 5 minutes | Real-time encoding tracks playback time and would otherwise tie up the tab |
| Maximum source pixels per side | 4096 px | Decoding caps the canvas pipeline |
| Maximum source area | 3840 x 2160 px | Combined dimension ceiling before geometry fails |
| Capture rate | Up to 30 fps | Higher source frame rates are downsampled to this ceiling |
| Output container | WebM (VP9 or VP8) | MP4 output requires a separate encoder; see MDN MediaRecorder for the codec limitations behind this |
When to Skip a Browser Resize
A local browser resize is not the right tool for every job, and recognizing those cases is part of doing the resize correctly in the broader sense. Move to a dedicated desktop encoder when you need frame-accurate delivery, footage longer than five minutes, MP4 rather than WebM output, color-managed grading, or strict control over bitrate and quality. The tool also does not upscale detail, remove black bars, crop a subject, preserve subtitles or multiple audio tracks, or bypass DRM, and it does not promise professional mastering. Treat the local resize as a fast way to bound a short clip to a clean WebM, not as a replacement for full editing software.
The pipeline itself is a sequence of standard browser APIs: the page validates bounded local metadata and integer target dimensions, picks contain-style versus stretch geometry, rounds dimensions to positive even values, draws decoded frames onto a canvas at 30 fps, attaches any exposed audio tracks, and records the canvas through MDN Canvas captureStream piped into MediaRecorder, before patching a finite duration and exposing a revocable local download URL. Understanding that pipeline is what lets you trust the saved WebM as a finished file rather than as a near-miss you have to re-render later.
Related reading: Plan the Steps Needed to Resize Video in Order.