UTM
UTM is an open-source virtual machine and system emulator for Apple devices. This page covers same-architecture virtualization, QEMU emulation, guest tools, shared folders and verified VM backups.
What UTM provides
UTM runs virtualized guests with matching architectures and emulates other architectures through QEMU on Apple devices. Virtualization is usually faster, while cross-architecture emulation broadens compatibility at a clear performance cost; choose the path from the host and guest architecture, not only the operating-system name.
Keep VM packages consistent
A .utm package should be copied only after the guest has fully shut down and disk writes have settled. Shared folders, external disks and cloud synchronization add separate consistency risks, so an imported copy should be started and checked before it becomes the backup of record.
Maintenance note
This page reviews UTM for Apple-device virtualization, QEMU emulation, guest integration and verified VM copies. Content review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave UTM to this cloud drive
Baidu Netdisk
Save UTM to this cloud drive
UTM guest setup and backup guide
Choose virtualization or emulation for a test guest, verify boot, network, display and one non-sensitive shared folder, then create a powered-off copy and start it as a validation step.
Before you start
- Prepare a legitimately obtained guest image, required key and enough disk and memory.
- Record host and guest CPU architectures and choose same-architecture virtualization when practical.
- Back up existing .utm packages and shared data outside any live synchronization folder.
Installation steps
- 01
Install the Apple-platform build
Install UTM for the device, confirm the version and understand the JIT and architecture differences between the full app and UTM SE.
- 02
Choose virtualization or emulation
Select the guest system and explicitly choose Virtualize or Emulate based on its architecture; a mismatch can prevent boot or make the guest unusably slow.
- 03
Allocate conservative resources
Start with modest CPU, memory and disk values, attach the installation image and set boot, display and network options while leaving enough resources for the host.
Quick start
- 01
Complete the guest installation
Install the guest onto its virtual disk, eject the installation image and confirm that it boots independently from the system disk.
- 02
Test guest integration
Install the matching guest tools, test resolution, clipboard, network, USB and one empty shared folder, keeping sensitive host paths out of the guest.
- 03
Copy after shutdown and verify
Shut down the guest normally, copy the full .utm package and any required external disk and start the imported copy to verify files and configuration.
Usage tips
- Same-architecture virtualization and cross-architecture emulation are different performance and compatibility paths.
- Virtual disks grow with guest writes; shared folders expose live host files and should not be treated as backups.
- Cloud synchronization of a running VM package can create inconsistent copies; power off first.
Troubleshooting and uninstall
Why is the guest black-screened or very slow?
Check image architecture, Virtualize or Emulate selection, boot order, memory and display device; cross-architecture emulation is expected to be slower.
Why are shared folders or clipboard integration missing?
Check guest tools, version compatibility, host permissions and guest mount state with a non-sensitive test folder before changing wider access.
- Back up powered-off guestsShut down every guest, copy .utm packages and external virtual disks and record network, CPU, memory and display settings; start a copy to verify it.
- Remove guests before the appConfirm guest names and backup locations before deleting them, then uninstall UTM and clear images or caches only after no external disk is still referenced.
Frequently asked questions
What is the difference between UTM virtualization and emulation?
Virtualization uses hardware acceleration for a compatible guest architecture, while QEMU emulation translates instructions for other architectures and is generally slower.
Is copying a running .utm package a reliable backup?
No. Shut down the guest and let disk writes finish before copying, then boot the copy to validate it.
Does UTM SE have the same emulation performance as the full app?
UTM SE avoids JIT requirements but uses a slower interpreter path and may include fewer architectures; choose it according to device limits and guest needs.
Does the download require an extraction code?
The Quark entry does not require one; the four-character code for the Baidu entry is shown beside its download entry.