Ask whether an online file converter is safe and you’ll get the same answer everywhere: look for HTTPS, check that they delete files afterwards, avoid sketchy sites. All reasonable. All beside the point.

Those answers quietly assume the file gets uploaded, and then argue about how well it’s guarded afterwards. But uploading isn’t a requirement of converting a file — it’s an architectural choice, and a growing number of tools don’t make it. So the useful question isn’t “do I trust their retention policy?” It’s the much simpler, much more checkable: did my file leave this computer at all?

You can answer that yourself in about a minute, without taking anyone’s word for it. Here are three tests, from most rigorous to easiest, and what we measured when we ran them on our own tool.

First: there are two completely different things called “online converter”

They look identical — a web page, a drop zone, a download button. Underneath they’re opposites.

	Server-side	In-browser (local)
Where the work happens	Their machines	Your machine
Your file	Uploaded, stored, processed, deleted on a timer	Never transmitted
Wait before work starts	Full upload time	None
Why there’s a size cap	Bandwidth and CPU cost them money	Only your device’s memory
Privacy rests on	Their policy and their security	Nothing leaving in the first place
Typical free-tier limit	100 MB – 1 GB	Multi-gigabyte

This is why the tests below work at all. The two designs leave completely different fingerprints, and neither can hide them.

Test 1: Watch the network tab (the rigorous one)

Your browser will tell you exactly what it sent. Nobody can spoof this — it’s your own browser reporting on itself.

1. Open the converter, then press F12 (or Cmd+Option+I on a Mac) and click the Network tab.
2. Click the clear button to empty the list.
3. Now add your file and run the conversion.
4. Sort by the Size column, largest first, and look at the biggest outgoing request.

If it uploads: you’ll see a POST request roughly the size of your file. A 200 MB video produces about 200 MB of outgoing data. It cannot be smaller — the bytes have to physically get there.

If it’s local: the largest outgoing request will be kilobytes. There is nowhere for a 200 MB payload to hide.

One false positive to know about

You will very likely see entries starting with blob:, sometimes with a large size and a 206 status. That is not an upload. A blob: URL is a local handle to data already in your browser’s memory, and the browser lists it in the Network panel because it’s a “fetch” in the technical sense. Nothing crosses the network. Local tools generate a lot of these — it’s a sign of local processing, not against it.

The entries that matter are ones with a real hostname and a request payload.

Test 2: The stopwatch test (no tools needed)

Uploads obey physics. Your home internet’s upload speed is usually far slower than its download speed, and a file cannot be processed on a server before it has finished arriving.

Your file	Minimum upload time at 10 Mbps up	At 50 Mbps up
100 MB	~80 seconds	~16 seconds
1 GB	~14 minutes	~3 minutes
4 GB	~55 minutes	~11 minutes

So: drop in a large file and watch what happens in the first few seconds. If a progress bar for the actual conversion starts moving immediately on a 2 GB file, no upload occurred — there wasn’t time. If you sit through a long “Uploading…” phase before anything else happens, you have your answer, and it was honest about it.

This is also the practical reason local tools handle big files at all. A site paying for bandwidth has to cap you; a tool using your own CPU has no such bill.

Test 3: Cut the network mid-job

The bluntest test: take the internet away and see if the work continues.

The sequencing matters, and most write-ups of this test get it wrong. Modern web apps load code in pieces, so the conversion engine may not download until the moment you actually select a file. Disconnect too early and you’re testing whether the page finished loading, not where the processing happens.

Do it in this order:

1. Open the page and select your file. Wait until the tool shows it’s ready to go.
2. Now turn off Wi-Fi or pull the cable.
3. Start the conversion.

A local tool runs to completion and hands you the file. A server-side tool stalls or errors out, because the thing doing the work is no longer reachable.

What we measured on our own tool

It would be a bit much to publish these tests without running them on ourselves. So we did, with the browser’s own network log as the instrument.

We fed a 4.19 MB MP4 into the video compressor on this site and recorded every outgoing request from the moment the file was selected until the download was ready.

• Total outbound data: 1,325 bytes. Two Google Analytics beacons — 311 bytes and 1,014 bytes.
• Bytes of video sent: zero. The largest request body in the entire run was one kilobyte.
• During the encode itself, requests to our own domain: zero. Not a single one while the progress bar was moving.

An accidental detail makes the point better than we’d have managed on purpose: during the test, those analytics beacons actually failed — our own host returned a 503 for them. The compression finished anyway, at full speed. The pipeline doesn’t just avoid sending your file; it doesn’t depend on the network at all once it’s running.

Two things we want to be straight about. First, yes — there is analytics, and there are ads on the page. That’s how a free tool with no signup and no upload cost stays free. What those beacons carry is page views and button clicks, not your file. Second, that 1,325 bytes is the honest full number, not “roughly nothing” — you can reproduce it with Test 1 in about a minute, and we’d rather you did.

The mechanism behind this isn’t exotic. The conversion runs as WebAssembly — a real build of FFmpeg compiled to run inside the browser tab, reading your file straight off your disk through the browser’s file API. We wrote up how that pipeline works in detail in How an In-Browser Audio Converter Actually Works.

That same percent-only telemetry is what powers our annual data report, The State of Everyday Video, 2026 — aggregate statistics over tens of thousands of files, with no filenames, file contents, or per-user profiles behind any of them.

What “we delete your files after 2 hours” actually buys you

Most reputable server-side converters do delete uploads, and most of them mean it. This isn’t an accusation. It’s about what kind of assurance you’re getting.

A deletion policy is a promise about something that already happened. Your file was transmitted, written to a disk you don’t control, and passed through logs, backups and whatever infrastructure sits in between. Keeping that promise depends on their retention actually working, their access controls holding, their vendors behaving and their company continuing to exist. Every one of those is probably fine. None of them is checkable by you.

A file that was never sent doesn’t need a promise. There is no copy to retain, breach, subpoena or forget about.

For a meme clip, the difference is academic — upload it anywhere. It stops being academic for the things people actually convert and compress: a signed contract, a passport scan, medical paperwork, an NDA’d client cut, unreleased footage, video of your kids. That’s also why we care most about it on the PDF compressor, which is where the genuinely sensitive documents show up.

Frequently asked questions

Are online file converters safe to use?

The mainstream ones are generally safe in the sense that they aren’t trying to harm you — the real variable is whether your file gets uploaded, and how much you care about that for this particular file. Run Test 1 above and you’ll know which kind of tool you’re using in about a minute, rather than relying on the marketing copy.

Does HTTPS mean my file is private?

No. HTTPS protects your file in transit, from people between you and the server. It says nothing about what happens once it arrives — who can read it, how long it’s kept, where it’s backed up. HTTPS is necessary, not sufficient, and it’s irrelevant to a tool that doesn’t transmit the file at all.

Why do most free converters cap file size?

Because every megabyte you upload costs them bandwidth, storage and CPU time. The cap is where the free tier stops being affordable, which is why it usually sits between 100 MB and 1 GB and why the paid tier raises it. Tools that run in your browser don’t have that cost, so their ceiling is your device’s memory instead — gigabytes rather than megabytes.

Can a website really convert video without a server?

Yes. WebAssembly lets real compiled code — including FFmpeg, the same engine behind most desktop video tools — run at close to native speed inside a browser tab. The page delivers the program; your own processor does the work. It’s the same reason a modern browser can run a video editor or a 3D game without installing anything.

Don’t trust it — check it

Every claim in this article, including ours, is verifiable from your own machine in under a minute. Open the network tab, drop in a file, look at the largest outgoing request. Do it to us, and do it to whatever tool you were about to paste a contract into.

If you’d like something to test it on, the video compressor, converters and PDF compressor here all run entirely in your browser — free, no signup, no watermark, and now you don’t have to take our word for it.

You dig out an old hard drive, a burned DVD-R or a folder your parents copied off a camcorder, and everything inside is .avi. Double-click it on a modern Mac and QuickTime shrugs. Drop it into your phone’s photo library and it refuses. Upload it to a website and you get “unsupported format”. The footage is fine — the container around it is thirty years old.

Converting AVI to MP4 fixes it permanently, and it usually makes the file dramatically smaller at the same time. Here’s what is actually inside those files, what you gain and lose in the conversion, and how to do it without uploading decades of family video to somebody else’s server.

Why your AVI files stopped playing

AVI (Audio Video Interleave) is a Microsoft container from 1992. A container doesn’t compress anything — it’s a box that says “here is a video track, here is an audio track, here is how they line up.” The problem isn’t the box itself. It’s that the codecs people put inside AVI files in 1998–2010 are the ones modern software quietly dropped support for.

Windows Media Player used to lean on system-wide codec packs, so any AVI played as long as you’d installed the right one. Browsers, phones and modern editors don’t work that way. They ship a fixed, small list of decoders — essentially H.264, HEVC, VP9 and AV1 — and anything else is simply not readable. Your DivX file didn’t break; the decoder that used to open it is no longer installed anywhere.

AVI also has real structural limits that modern containers don’t: no native support for modern variable frame rates, awkward handling of B-frames, a 2GB ceiling in the original spec (raised, but inconsistently implemented), and no standard place to store the rotation flag or chapter data. MP4 handles all of it.

What is actually inside your AVI file

“AVI” tells you almost nothing about the video. Before you convert, it helps to know which of these you have — it predicts both how much smaller the MP4 will be and whether quality is a concern at all.

Codec inside the AVI	Where it came from	Typical size	What conversion changes
DV / DVCPRO	MiniDV camcorder tapes captured over FireWire	~13 GB per hour	Huge size win — 85–95% smaller, no visible loss
MJPEG	Early digital cameras, webcams, some dashcams	~4–6 GB per hour	Big size win — every frame is a separate JPEG, so there’s a lot of redundancy to remove
DivX / Xvid (MPEG-4 Part 2)	Downloaded video and DVD rips, roughly 1999–2010	700 MB–1.4 GB per movie	Modest size win, mainly a compatibility fix
MPEG-1 / MPEG-2	Video CDs, DVD extractions, TV capture cards	~2–4 GB per hour	Large size win, no visible loss
WMV / VC-1	Windows Movie Maker exports, old screen recorders	Varies widely	Compatibility fix; size depends on the original bitrate
Uncompressed / raw	Scientific capture, some editing intermediates	50 GB+ per hour	Enormous size win — often 99% smaller

The pattern: the older and less compressed the codec, the more you gain. Files that were already aggressively compressed (DivX, Xvid) convert mostly for compatibility, and you should not expect them to shrink much without giving up quality.

A worked example: 20 minutes of camcorder tape

The most common “why is this file so enormous” case is DV-AVI — footage captured off a MiniDV camcorder. DV is a fixed-bitrate format: 25 Mbit/s for video plus uncompressed audio, which works out to roughly 216 MB per minute no matter what you shot.

• Source: 20-minute DV-AVI, 720×480, 4.3 GB
• Output: H.264 MP4 at about 2.5 Mbit/s with AAC audio — roughly 380 MB
• Result: ~91% smaller, and it now plays on a phone, in a browser and in every editor

That is not a trick. DV was designed in the early 1990s to be edited frame-by-frame off tape, so it compresses each frame independently and never looks at the frame before it. H.264 encodes the differences between frames instead, which is why an interview where only the subject’s face moves compresses so well. You’re not throwing away detail so much as stopping the file from storing a nearly identical picture 30 times a second.

The same logic applies to MJPEG from old cameras: it’s literally a sequence of JPEG stills, and a modern codec finds enormous redundancy between them.

How to convert AVI to MP4 in your browser

Old home video is exactly the kind of footage you don’t want sitting in a stranger’s upload queue. Most online converters take your file, send it to a server, process it there and hand you back a download link — which means a copy of your family archive lives somewhere you can’t audit, for as long as their retention policy says.

The AVI to MP4 converter on RedPandaCompress works differently: the conversion runs entirely inside your browser tab using WebAssembly FFmpeg. Nothing is uploaded, nothing is queued, and there’s no per-file pricing because we’re not paying for the compute — your own machine does the work.

1. Open the converter and drop your AVI onto the page — or pick several at once.
2. Conversion starts immediately. There’s no upload progress bar because there’s no upload; the first thing you see is the encoder working.
3. Download the MP4. Output is always H.264 video with AAC audio — the combination that plays on effectively every device made in the last fifteen years.

Files up to 8 GB work on desktop browsers and 2 GB on mobile, with no signup, watermark or daily quota. Recognized inputs cover the codecs in the table above — MPEG-4/DivX/Xvid, MJPEG, MPEG-1/2, WMV/VC-1, DV and raw video, with MP3 or PCM audio. If a file uses something genuinely exotic you get a clear error rather than a silently broken output.

If your archive is a mix of formats, the same engine handles MOV, MKV, WebM and WMV in one place — see our converter overview for the full set.

Will converting cost you quality?

Honest answer: technically yes, practically almost never for AVI sources.

Some conversions are lossless. When a file already contains H.264 video — most MOV and MKV files, for instance — the streams can simply be moved into an MP4 container without being decoded, which is instant and bit-identical. AVI almost never holds H.264, so an AVI conversion is a real re-encode: decode the old codec, encode H.264.

What saves you is the gap in efficiency. H.264 is roughly two to three times more efficient than MPEG-4 Part 2 (DivX/Xvid) and far ahead of DV or MJPEG, so an H.264 encode at a fraction of the original bitrate still holds more detail than the source ever did. The one case to be careful about is a DivX or Xvid file that was already compressed hard — squeezing it further will show. For those, convert for compatibility and leave the bitrate generous rather than chasing a smaller number.

If you’re curious why H.264 and not something newer, we compared the options in H.264 vs H.265 vs AV1. The short version: newer codecs are smaller, but H.264 is the only one you can hand to anyone and be confident it just plays.

AVI vs MP4 at a glance

	AVI	MP4
Released	1992	2001
Plays on phones	Rarely	Everywhere
Plays in browsers	No	Yes
Accepted by messengers and web uploads	Usually rejected	Standard
Typical codecs	DivX, Xvid, MJPEG, DV, MPEG-2	H.264, HEVC, AV1
Streaming-friendly	No	Yes (fast-start)
File size for the same footage	Baseline	Often 50–95% smaller

Frequently asked questions

Can I convert AVI to MP4 without re-encoding?

Only in the rare case where the AVI already contains H.264 video — some capture cards and screen recorders produced these. Nearly all real-world AVI files hold DivX, Xvid, MJPEG, DV or MPEG-2, none of which MP4 players can decode, so the video has to be re-encoded. That’s also where the size savings come from.

Why is my AVI file so large compared to a modern video?

Because the old codecs mostly compress each frame on its own instead of storing only what changed between frames. DV runs at a fixed 25 Mbit/s regardless of content; a modern H.264 encode of the same shot might need 2–3 Mbit/s. Same picture, a fraction of the data.

Is it safe to convert old family videos online?

It depends entirely on whether the tool uploads your file. Server-side converters transmit and store a copy of your footage. RedPandaCompress runs the conversion locally in your browser with WebAssembly — the file never leaves your device, so there’s nothing to store, leak or delete later. You can confirm it yourself: once your file is loaded and ready to convert, disconnect from the network — the conversion still finishes. We wrote up that test and two others, with measured results, in Are Online File Converters Safe?

What happens to the audio track?

MP3 audio is carried over unchanged where possible. Uncompressed PCM audio — common in DV and MJPEG captures, and a real contributor to those file sizes — is converted to AAC, which is inaudibly different and a fraction of the size. The result is a single MP4 with one video and one audio track.

Convert the archive once, keep it forever

An AVI file is a countdown: every year, fewer programs can open it. Converting to H.264 MP4 gets your footage into the one format that phones, browsers, TVs, editors and every upload form agree on — and for camcorder and camera-era files, it typically reclaims 80–95% of the disk space at the same time.

Convert your AVI files to MP4 free at RedPandaCompress — unlimited, no signup, no watermark, and nothing ever leaves your computer.