Yes — you can resize a video without uploading a file by running a browser-based resizer such as Video Resizer on your own device. The entire workflow lives inside the current browser tab: JavaScript decodes the local source, draws each frame onto an HTML canvas at the new pixel dimensions, and re-encodes the canvas to a downloadable WebM through the browser's built-in MediaRecorder. Because the bytes never travel to a remote endpoint, the source file stays private, works without an account, and remains usable on spotty connections where uploading 500 MiB would be impractical. You do need a current desktop browser that exposes canvas captureStream (Chrome, Edge, or Firefox) and a WebM-capable MediaRecorder, which is what the tool probes for before it lets you start. This guide covers the exact inputs the tool accepts, how Fit and Stretch modes differ, the pixel and size limits you must respect, and when you should step up to a dedicated desktop encoder instead.
Why Browser-Based Resizing Works Without Uploading
Modern browsers ship with the same low-level media primitives that desktop encoders rely on, so a local resize no longer requires installing FFmpeg or paying for a server-side service. When you pick a file with the file picker, the File API hands the bytes to your tab; nothing is POSTed to a remote endpoint. The browser then decodes the source with the same codec pipeline it already uses to play the video, draws every frame onto an offscreen canvas that has been resized to your target width and height, and uses canvas captureStream together with MediaRecorder to capture and re-encode the canvas at up to 30 fps. The resulting blob sits in memory until you click Download, at which point the browser offers a revocable local URL.
That architecture has three practical consequences worth understanding. First, privacy is structural rather than promised: the source cannot leak because it never leaves the File object. Second, the encode runs in real time, so a one-minute clip takes roughly one minute to finish on a mid-range laptop. Third, the output is constrained to whatever the browser's VP9 or VP8 WebM recorder can produce, which is why the result is always a WebM regardless of what you upload.
If you are working from a laptop and want a walk-through that focuses on that device specifically, see Video Resizer on Laptop: Resize Locally in Your Browser.
What Resizing Actually Changes in Your File
Resizing here is a real re-encode, not a metadata edit. The tool does not simply rewrite a header to claim a new resolution; it redraws each frame at the requested dimensions, which means the pixel data is genuinely transformed and the file is rebuilt around the new size. Several side-effects follow.
- Quality: Encoder choices are made by the browser, so output sharpness, blocking, and color response are determined by the VP9 or VP8 configuration MediaRecorder selects, not by your source settings.
- Bitrate: The tool uses a bounded bitrate appropriate for the target dimensions; you cannot dial in an exact kilobit-per-second value.
- Frame timing: Frames are captured at up to 30 fps, so a 60 fps source is downsampled in time.
- Audio: Any audio tracks the browser exposes from the source are muxed into the output; multi-channel layouts, surround metadata, and per-track language tags are not preserved as authored.
- Subtitles, chapters, multiple video tracks, and DRM: Not supported. The source must be unencrypted and is treated as a single video stream plus available audio.
- Color metadata, EXIF, GPS, and sidecar data: Stripped during the canvas re-encode, since the canvas carries only pixel data.
Expect the output WebM to look reasonable but not identical to a master file produced by FFmpeg, HandBrake, or a commercial NLE. That trade-off is the cost of doing the work locally in your tab.
How to Resize a Video Locally in Your Browser
- Open the Video Resizer tool in a current desktop browser such as Chrome, Edge, or Firefox.
- Click the file picker and choose one supported local video: MP4, WebM, MOV, M4V, or Ogg. Wait for the browser to finish reading metadata before continuing.
- Enter the maximum width and maximum height in whole pixels. Each value must be an integer from 2 to 1920.
- Choose a mode: Fit to preserve the source aspect ratio inside the bounding box, or Stretch to use your exact width and height even if the picture distorts.
- Click Resize video. Keep the tab focused and the page open during the real-time encode.
- When the recorder finishes, click Download to save the resulting WebM. The file lives at a revocable local URL and never touches a server.
If you enter odd dimensions, the tool rounds each value down to the nearest even pixel so common browser encoders behave reliably. For example, a request of 1281 × 721 becomes 1280 × 720 internally before the encode starts, and 801 × 501 becomes 800 × 500.
Fit vs Stretch: Which Mode to Pick
| Aspect of comparison | Fit mode | Stretch mode |
|---|---|---|
| Aspect ratio | Preserved from source | Matches your exact numbers, can distort |
| What the entered dimensions mean | A bounding box (max width × max height) | Exact target dimensions |
| When the source ratio differs | Scales by the smaller side; leaves the rest of the box empty | Squashes or stretches to fill |
| Cropping | Never crops | No cropping, but distortion may be visible |
| Best for | Sharing on platforms that enforce ratios (YouTube, Instagram, TikTok) | Matching a fixed canvas like a banner or background plate |
Worked example for Fit mode. Suppose your source is 1920 × 1080 and you request 800 × 600. The tool computes the smaller of the two scales: min(800 ÷ 1920, 600 ÷ 1080) = min(0.4167, 0.5556) = 0.4167. Multiplying the source dimensions by that scale gives 1920 × 0.4167 ≈ 800 and 1080 × 0.4167 ≈ 450, so the output is 800 × 450 — a 16:9 frame that fits inside your 800 × 600 box without cropping.
Worked example for Stretch mode. With the same source and a request of exactly 800 × 600, the tool writes those dimensions directly. The horizontal axis is compressed from 1920 to 800 pixels and the vertical axis from 1080 to 600, so the picture no longer matches the source ratio and will look horizontally squashed. Use Stretch only when the destination genuinely requires those exact dimensions.
Input and Output Limits to Know Before You Start
| Item | Limit |
|---|---|
| Accepted source formats | MP4, WebM, MOV, M4V, Ogg (must decode in your browser) |
| Source file size | Up to 500 MiB |
| Source duration | Up to 5 minutes |
| Source dimensions | No side longer than 4096 px; total area no greater than 3840 × 2160 |
| Target width / height entry | Whole integer, 2 to 1920 |
| Odd target dimensions | Rounded down by 1 pixel so the encoder receives even values |
| Output container / codec | WebM with VP9 or VP8 video, plus any browser-exposed audio |
| Output frame rate | Up to 30 fps captured from the canvas |
| Processing time | Approximately real-time (a 1-minute clip takes about a minute) |
If the recorder produces no data, the source codec is unsupported, or the metadata exceeds the limits above, the tool fails visibly instead of giving you a misleading download. Common triggers include HEVC-only MOVs from older iPhones, files larger than 500 MiB, or sources that exceed 4096 pixels on a side. Eight independent geometry fixtures cover landscape, portrait, square, same-ratio, bounding-box, stretch, and odd-dimension cases so the resize path is exercised before any output is offered.
When a Desktop Encoder Is the Better Choice
Browser-based resizing covers a wide range of casual needs, but it is not a replacement for a full encoder pipeline. Choose a desktop tool instead if you need any of the following.
- MP4 output. The local tool only emits WebM. If your downstream system requires H.264 in an MP4 wrapper, you must transcode elsewhere.
- Exact bitrate control. MediaRecorder picks its own bitrate; you cannot specify a target kilobit-per-second.
- Frame-accurate delivery. Canvas capture at 30 fps cannot guarantee sample-accurate timing for broadcast or master-quality work.
- Long-form footage. The five-minute cap and the real-time encode cost make anything beyond a short clip impractical.
- Color-managed workflows. Rec. 709 / Rec. 2020 tags, HDR metadata, and ICC profiles do not survive the canvas re-encode.
- Subtitles, multiple audio tracks, or chapter markers. Only the audio the browser exposes is preserved; everything else is dropped.
- DRM-protected sources. Encrypted content will not decode and must be transcoded from a legitimate master on a system you control.
For any of those cases, run the source through FFmpeg, HandBrake, or a commercial NLE on a machine you own. Use the browser resizer when privacy, speed of setup, and not installing anything are the priority — and only on media you have the right to edit.
If you're weighing options, Can I Trim Video Without Uploading a File? covers this in detail.