ASF to ASF Converter

How to Re-encode ASF Video Online

1. Upload Your ASF File: Drag and drop or click "+ Add Files" to load .asf files from your computer. Batch upload is supported — re-encode a folder of camera DVR exports or Windows Media archives with the same settings in one pass.
2. Pick a Video Codec: Default is WMV2 — the standard Windows Media codec that ASF was built around. Switch to H.264 for ~50% smaller files at the same quality, H.265 for another ~40% reduction, or pick from AV1, VP8, VP9, MPEG-4, DivX, XviD, MJPEG, Theora, MSMPEG4, or H.263 if a downstream player needs that specific codec inside the ASF wrapper.
3. Tune Quality, Resolution, or Trim (Optional): Use the Video Quality Preset dropdown (Lowest/Low/Medium/High/Highest), set a CRF value (0-51 for H.264/H.265, 0-63 for VP9/AV1) on the Constant Quality slider, set a Constant or Variable Bitrate, pick a Video Resolution Preset (144p, 240p, 360p, 480p, 576p, 720p, 1080p, 1440p, 2160p, 4320p), scale by percentage, or use Video Trim with start time and duration. Audio Codec defaults to WMAV2 with WMAV1, AAC, MP3, AC3, Opus, FLAC, Vorbis, AMR, and Speex available.
4. Re-encode and Download: Click "Convert" and your re-encoded ASF downloads in seconds. Files process in your browser session — no sign-up, no watermark, no upload to a third-party server.

Why Re-encode ASF?

ASF (Advanced Systems Format) is Microsoft's container introduced in 1999 as the wrapper for Windows Media Video and Windows Media Audio streams. The same .asf file might hold an old WMV1/WMAV1 Windows Media 7 recording, a WMV2/WMAV2 stream from a Windows XP-era encoder, or — increasingly — a more modern codec like H.264 or AAC tucked inside the ASF container for legacy compatibility. Re-encoding the same ASF gives you control over codec, bitrate, resolution, and length without changing the extension that legacy Windows Media servers, IP camera DVR software, and older SCADA/industrial playback systems still expect.

• Standardize codec across a Windows Media library — A folder pulled off an old Windows XP machine might mix WMV1, WMV2, WMV3, and MSMPEG4 video streams. Re-encoding the whole set to a single codec (typically WMV2 for legacy or H.264 for modern players) makes a library indexable, predictable, and easier to seek.
• Shrink IP camera and surveillance archives — Many older IP cameras and DVRs (Hikvision, Dahua, Axis legacy firmware) save evidence as ASF. A 24-hour 1080p WMV2 capture can run 8-15GB. Re-encoding to H.264 at a lower CRF cuts that 50-70% while keeping the .asf extension the camera management software expects when re-importing.
• Hit upload limits without leaving ASF — Some legacy enterprise content systems (older SharePoint, internal LMS platforms) only accept .asf upload. Drop the bitrate or resolution to land under the 100MB / 250MB / 1GB limits these systems impose without re-wrapping the file.
• Downscale 1080p captures for embedded WMV players — Older dashboards and kiosk systems running Windows Media Player 9-12 struggle with 1080p WMV2. Downscaling to 720p or 480p inside the same ASF container restores smooth playback on the original hardware.
• Trim out dead time — Surveillance ASF clips often include hours of static footage. Use Video Trim to keep just the 30-60 second incident window and re-encode it cleanly, dropping the file from gigabytes to megabytes for evidence sharing or court submission.
• Re-encode to fix a partially corrupted ASF — When an ASF file plays for the first few seconds and then stalls, re-encoding the readable portion produces a clean container with valid index headers, often recovering content that won't seek in Windows Media Player.
• Switch from WMAV1 to WMAV2 or AAC audio — Legacy WMAV1 audio can crackle on modern decoders. Re-encoding the audio track to WMAV2 or AAC inside the same ASF container fixes playback while keeping the file format intact.

ASF Codec Comparison: WMV2 vs H.264 vs H.265

CRF Quality Quick Guide (H.264/H.265 inside ASF)

Frequently Asked Questions

Why would I convert ASF to ASF instead of just keeping the original?

The container stays .asf, but the codec, bitrate, resolution, and length inside can all change. A WMV2 ASF at 1080p/8Mbps and an H.264 ASF at 720p/2Mbps are both valid .asf files but differ massively in size and compatibility. Re-encoding lets you swap codec (WMV2 ↔ H.264 ↔ H.265), drop bitrate, downscale, or trim — all while keeping the extension that legacy Windows Media servers, DVR management software, and older corporate playback tools require.

Should I keep WMV2 or switch to H.264 inside the ASF?

Keep WMV2 only if your downstream system explicitly requires Windows Media codecs (older Windows Media Services streaming servers, certain SCADA dashboards, kiosk firmware locked to a specific codec). For everything else, H.264 inside ASF gives you ~50% smaller files at equivalent visual quality and decodes natively on every device made since 2010. H.265 saves another ~40% but encodes slowly and isn't universally supported by older ASF-aware tools.

Can I re-encode an ASF that won't play normally?

Often yes. ASF files corrupted in the index or trailer can frequently be re-encoded by reading the valid frames and writing a fresh container. The output gets clean index headers and seekability restored. Re-encoding cannot recover frames that are missing or unreadable in the source — it can only rebuild the wrapper around what's still decodable.

What audio codec should I use inside ASF?

WMAV2 is the safe default — it's the modern Windows Media Audio codec that every WMP build since 2001 plays without complaint. Switch to AAC if a downstream tool prefers it (some non-Microsoft players handle AAC-in-ASF more reliably than WMA). MP3 inside ASF works but is less common; AC3, Opus, FLAC, and Vorbis are available when a specific workflow demands them.

Will re-encoding reduce quality?

Every lossy re-encode loses some data. The loss is small at low CRF / high bitrate settings and barely visible at CRF 23 or below for H.264. Re-encoding from an already-compressed source (a WMV2 file at 1Mbps) and dropping the bitrate further compounds the loss. For best quality, re-encode from the highest-quality source you have and aim to keep the new bitrate within ~70% of the original unless you specifically need a smaller file.

Will WMV-specific metadata, DRM, and stream attributes survive?

Standard ASF metadata (title, author, description, copyright) carries through re-encoding. DRM-locked ASF files — older Microsoft PlaysForSure / Windows Media DRM content from 2003-2008 — cannot be re-encoded without an authorized key chain and will fail or produce a silent file. Multi-stream ASF files keep the primary video and audio tracks; secondary script streams or non-standard payloads are dropped.

Is there a file size limit?

XConvert processes files in your browser session, so the practical limit is your device's available memory. Most modern laptops handle 1080p ASF files up to 2-4GB without trouble. For very large surveillance captures, downscale resolution first, trim to the segment of interest, or split into chunks before re-encoding.

How is this different from converting ASF to another format?

Re-encoding ASF to ASF keeps the .asf extension and container that legacy Windows Media systems require. If you don't need to stay in ASF, Convert ASF to MP4 gives you the universal modern container, Convert ASF to AVI targets older video editors, or Convert ASF to WMV drops the streaming wrapper while keeping Windows Media codecs.

Does the converter work offline once the page loads?

Yes. After the page and conversion engine load, the actual encoding runs locally via WebAssembly. You can disconnect from the network mid-conversion and it will still finish — files never leave your browser.