Cut ASF files by setting start and end times. Free, no quality loss.
Process files in seconds with our optimized servers
Frame-accurate cuts with intuitive timeline controls
Maintain original quality with smart re-encoding
.asf (or .wmv / .wma-extensioned ASF) clip from a Windows Media Encoder capture, a Windows XP / Vista / 7 Media Center DVR-MS export, an older corporate-training video, or an archive of camcorder footage from a Windows machine. Batch is supported — drop multiple ASF files and apply the same cut range to each.12.5) or HH:MM:SS.sss format (00:01:30.500). Cuts are frame-accurate: XConvert decodes the clip and re-encodes the kept range at the visually-lossless default quality preset, so the output starts exactly at your mark instead of snapping to a keyframe. Pick an explicit codec (H.264, MPEG-4, etc.) only if you also want to change format in the same pass.ASF (Advanced Systems Format, originally "Advanced Streaming Format") is the Microsoft container released publicly on 26 February 1998 — the wrapper Windows Media Video (WMV), Windows Media Audio (WMA), and VC-1 streams ride inside. ASF was engineered for HTTP and MMS streaming with built-in stream prioritization, scalable media types, and the framework for Windows Media DRM. Cutting an ASF clip is useful for:
.asf or .wmv. Pull the 90-second segment you need without spinning up a Windows VM to re-encode..dvr-ms, a DVR-MS variant of the ASF container. Many users rename .dvr-ms to .asf for tool compatibility, then cut to the commercial break or single scene worth keeping.For a different output container without trimming, see ASF to MP4, ASF to AVI, or ASF to WMV. To compress without changing the duration, see Compress ASF. For the same workflow framed as in/out points, see Trim ASF.
The terms are conflated constantly. Here is what each actually refers to.
| Property | ASF | WMV | MP4 |
|---|---|---|---|
| Type | Container (wrapper) | Video codec family | Container (wrapper) |
| Standardized by | Microsoft (proprietary, open spec) | Microsoft / SMPTE 421M for VC-1 | ISO/IEC 14496-14 |
| Common file extension | .asf (mixed), .wmv (video), .wma (audio) |
Always inside .asf / .wmv |
.mp4, .m4v, .m4a |
| Typical video codec | WMV 7/8/9, VC-1, occasionally MPEG-4 | n/a (is itself a codec) | H.264, H.265, AV1 |
| Typical audio codec | WMA, WMA Pro, occasionally MP3 | n/a | AAC, Opus, ALAC |
| DRM framework | Windows Media DRM (ECC + RC4 + SHA-1) | Same (inherits ASF) | None native (FairPlay / Widevine externally) |
| Native playback (2026) | Windows Media Player legacy, VLC, MPC-HC | Same as ASF | Every modern browser, iOS, Android, smart TV |
| Streaming origin | MMS, IIS Smooth Streaming (legacy) | Same | HLS, DASH, plain HTTP progressive |
A .wmv file is an ASF container carrying a WMV-codec video stream. A .asf file is the same container but does not promise any specific codec inside — the spec itself says "the format does not specify with which codec the video or audio should be encoded." Cutting either one is the same operation on the container level.
| Property | Stream copy (other tools) | Re-encode (how XConvert cuts) |
|---|---|---|
| Speed | Seconds for any file size | Proportional to clip length |
| Quality | Bit-identical to source | Visually-lossless default preset — visually indistinguishable |
| Cut precision | Snaps to nearest keyframe (commonly 2-8 s for WMV) | Frame-accurate |
| Output codec | Same as source (WMV / VC-1 / WMA) | Default, or your explicit Video Codec pick |
| Audio | Original WMA / WMA Pro / MP3 preserved | Re-encoded |
| Best for | Desktop tools where keyframe snapping is acceptable | Every cut on this page — frame-accurate start, optional codec swap or smaller file |
Windows Media Encoder defaults wrote a keyframe ("clean point" in ASF parlance) every 8 seconds for streaming profiles and every 2-4 seconds for higher-bitrate VOD profiles. Stream-copy cutters land on the nearest preceding clean point — ask for 00:01:13 with the nearest one at 00:01:08 and their output starts there. XConvert re-encodes the kept range, so the cut starts at the exact timestamp you typed.
No — the cut is re-encoded. XConvert decodes the selected range and re-encodes it at the visually-lossless default quality preset, which is exactly what makes the cut frame-accurate: ASF files produced by Windows Media Encoder 9 place keyframes ("clean points") only every 2-8 seconds, so a no-re-encode cut would have to snap back several seconds from the timestamp you typed. Here it starts on the exact frame you request, and at the default settings the output is visually indistinguishable from the source.
Generally yes — the output keeps the ASF container and plays in Windows Media Player Legacy on Windows 11, VLC on every platform, and MPC-HC. Note that the modern Windows 11 "Media Player" app dropped some legacy WMV profile support; if it refuses to play the cut, VLC will, and a one-pass conversion to ASF to MP4 makes the clip play natively on macOS, iOS, Android, and every browser.
ASF and its WMV / VC-1 codecs are Microsoft proprietary, and neither macOS QuickTime nor iOS ship a decoder. VLC for macOS and iOS does play ASF, but for general-purpose sharing the safer route is to cut first, then transcode the cut clip via ASF to MP4 (H.264 / AAC). That output plays on Safari, Chrome, the native iOS Photos app, and every smart TV.
.dvr-ms from Windows Media Center — will this tool cut it?The accepted extension here is .asf. DVR-MS is a Microsoft variant of the ASF container used by Windows XP / Vista / 7 Media Center to record live TV — internally it is an ASF wrapper with extra timestamp and closed-caption objects. Renaming the file from .dvr-ms to .asf works for most cuts because the underlying packets are still valid ASF that the decoder can read; if your file uses MS-protected content (DRM-encrypted recordings of premium cable), no online tool — ours included — can cut it without the original license.
No. Windows Media DRM encrypts the media payload with keys bound to the original Windows license server, and the cutter has to decode that payload to re-encode the kept range. Decrypting without the license is not something any legitimate tool will do. Strip DRM at the source (in the original Windows Media Player or with Microsoft's own license-export workflow where allowed) before cutting.
There is no fixed cap on our side. Cutting runs on our servers, so the practical ceiling is upload size and connection speed and patience. Multi-GB DVR-MS / ASF recordings cut fine on our servers regardless of your device; on phones and Chromebooks the main limit is upload speed, so smaller clips upload faster. Processing time scales with the length of the kept range, not the full recording — a short clip out of a 4-hour archive capture processes quickly because only the kept range is re-encoded.
Yes. Cut the ASF to the segment you want, then run ASF to MP3 or another audio target on the result. Cutting first is faster because the audio extraction only has to process the trimmed range, not the full source. If your source is .wma (audio-only ASF) the audio extraction reduces to a stream-copy plus container swap.
Same operation in practice. Some editors reserve "trimming" for shaving the head and tail of a continuous segment, and "cutting" for extracting a sub-range by start + duration. XConvert handles both patterns — set start time to your in-point and duration to how much to keep. See Trim ASF for the same workflow framed as in/out points, or Compress ASF if you want size reduction without changing the duration.
If a Windows-only legacy player, an internal IIS Smooth Streaming pipeline, or a compliance archive requires ASF, keep ASF. Otherwise, MP4 with H.264 / AAC is smaller for equivalent quality, plays natively on every modern phone and browser, and uploads cleanly to YouTube, Google Drive, and WhatsApp. The recommended workflow is: cut first, then run ASF to MP4 on the cut clip — considerably faster than transcoding the full source and trimming the MP4 afterward, since only the kept range gets processed.