DESKTHEMEPACK File Documentation

Summary

A Windows Desktop Theme Pack file is a single bundle that carries a complete desktop look: wallpapers, accent colour, a sound scheme and cursors. It is a Microsoft Cabinet (CAB) archive, introduced with Windows 8 in 2012 as the successor to the Windows 7 .themepack. Double-click a .deskthemepack on Windows 8, 10 or 11 and the theme applies instantly. To pull out just the wallpapers, rename a copy to .cab and open it with 7-Zip or File Explorer.

Technical details

FeatureValue
Full nameWindows Desktop Theme Pack
File extension.deskthemepack
MIME typeapplication/octet-stream
Format typeMicrosoft Cabinet (CAB) archive bundling a .theme file plus assets
DeveloperMicrosoft
Introduced2012 (Windows 8), successor to the Windows 7 .themepack
Open standardNo — Windows-only, proprietary
Container / base formatMicrosoft Cabinet (CAB)
Magic number4D 53 43 46 (ASCII MSCF)
Byte orderLittle-endian
Central settings file*.theme — plain-text INI
Bundled assetsWallpaper images, sound scheme (.wav), cursors (.cur/.ani)
Applies onWindows 8, 10 and 11
Install location%LocalAppData%\Microsoft\Windows\Themes
Extract byRename copy to .cab, open with 7-Zip or File Explorer
Related extensions.themepack, .theme, .cab, .msstyles
Specificationlearn.microsoft.com/windows/win32/controls/themesfileformat-overview
File signature (magic bytes)
4D 53 43 46

Offset 0, 4 bytes, ASCII MSCF (Microsoft Cabinet File). A .deskthemepack is a CAB archive, not a ZIP, so it opens with the same signature as any .cab. The CFHEADER continues with the cabinet size at offset 8 and the version bytes 03 01 (minor 3, major 1) at offset 24. To extract the wallpapers, rename a copy to .cab (not .zip) and open it with 7-Zip or Windows File Explorer.

What is a .deskthemepack file?

A Windows Desktop Theme Pack is Microsoft’s packaged desktop-theme format, introduced with Windows 8 in 2012 as the successor to Windows 7’s .themepack. It lets a complete look-and-feel travel as a single file. Inside are the desktop wallpaper or wallpapers, the accent and window colour, a sound scheme and, when included, a set of mouse cursors. The desk prefix marks the Windows 8-and-later version, which added support for slideshow and multi-monitor wallpapers that the older .themepack could not express.

The format does one job: it changes how the desktop looks. It contains no programs and alters nothing except personalization settings. People meet a .deskthemepack when they download a theme from the Microsoft Store or the old Windows themes gallery, or when someone shares one. Two things trip users up, and both come from the same fact: this is not a ZIP. It is a Microsoft Cabinet archive, which changes how you get the files out, and it is Windows-only, so there is nothing to open on a Mac or phone.

The CAB container and the MSCF header

A .deskthemepack is a Microsoft Cabinet (CAB) archive. Every CAB begins with the four ASCII bytes MSCF (4D 53 43 46) at offset 0, which is the reliable way to identify the file regardless of its extension. This matters because the widespread advice to “rename it to .zip” is wrong for modern theme packs: a CAB is not a ZIP and a ZIP tool will refuse it unless the tool also understands CAB. The correct move is to rename a copy to .cab.

The opening structure of the archive, the CFHEADER, records the essentials a cabinet reader needs before it touches any file:

offset  size  field
  0      4    signature 'MSCF' (4D 53 43 46)
  4      4    reserved (must be 0)
  8      4    cbCabinet: total size of this cabinet, in bytes
 12      4    reserved (must be 0)
 16      4    coffFiles: offset of the first CFFILE entry
 20      4    reserved (must be 0)
 24      1    versionMinor = 3
 25      1    versionMajor = 1
 26      2    cFolders: number of CFFOLDER entries
 28      2    cFiles:   number of CFFILE entries
 30      2    flags (bit 0 prev cabinet, bit 1 next, bit 2 reserved fields)

After the header come the folder and file tables (CFFOLDER and CFFILE entries), then the compressed data blocks (CFDATA). CAB typically compresses with MSZIP (a DEFLATE variant) or LZX. All multi-byte fields are little-endian. The reader uses coffFiles at offset 16 to jump straight to the file directory, then decompresses only the blocks it needs — which is exactly what happens when a CAB-aware tool lets you copy one wallpaper out without unpacking the whole theme.

The .theme settings file inside

The heart of the pack is a single *.theme file, and unlike the binary cabinet around it, this is plain text in INI format. It does not contain any images or sounds itself; it is a manifest of settings and references, organised into named sections, that points at the asset files travelling alongside it in the same cabinet.

[Theme]
DisplayName=My Theme

[Control Panel\Desktop]
Wallpaper=%SystemRoot%\...\img1.jpg
TileWallpaper=0
WallpaperStyle=10

[Slideshow]
Interval=1800000
Shuffle=1
ImagesRootPIDL=...

[Control Panel\Colors]
Background=0 0 0

[VisualStyles]
...
[Sounds]
[Cursors]

The [Control Panel\Desktop] section names the wallpaper and how it is scaled. The [Slideshow] section is the Windows 8 addition that lets a theme rotate through several wallpapers on a timer, which is why the newer format needed a new extension: a Windows 7 .themepack reader would not understand it. The remaining sections reference the accent colour, the visual style, the sound scheme and the cursor scheme. Because the .theme file only references its assets, it needs those images, sounds and cursors present to apply correctly — which is the whole point of bundling everything into one cabinet.

What happens when you apply a theme pack

Double-clicking a .deskthemepack hands it to the Windows theme handler. Windows opens the cabinet, extracts the bundled resources into your user profile under %LocalAppData%\Microsoft\Windows\Themes, reads the .theme manifest, and switches the desktop to match: it sets the wallpaper (or starts the slideshow), applies the accent colour, installs the sound scheme and swaps the cursors. The Personalization page (Settings › Personalization › Themes) opens so the new theme appears as the active one. Nothing is installed as a program and nothing runs; the operation is entirely a personalization change scoped to the current user.

This is also why a .deskthemepack that refuses to do anything on double-click is almost always an environment problem, not a broken file. Either the machine is on an unsupported Windows edition, or the file association for .deskthemepack has been changed. In both cases the assets are still reachable by treating the file as the cabinet it is.

Extracting just the wallpapers

The single most common task after “apply the theme” is “I only want the wallpapers.” Because the pack is a CAB, the images inside are already ordinary JPG or PNG files — there is no conversion to do, only extraction. Make a copy of the file, change the copy’s extension from .deskthemepack to .cab, then open it. Windows File Explorer can browse a CAB natively and let you copy files out; 7-Zip and any other CAB-aware archiver do the same. Pull out the image files and set them as your background on any device, including a Mac or phone where the theme itself cannot run.

The reason to insist on .cab rather than .zip is practical: a plain ZIP utility that does not know CAB will report the renamed file as corrupt, because the MSCF header is not a ZIP header. Renaming to the format the bytes actually are is what makes the extraction work.

Theme pack versus the older themepack

Both .themepack (Windows 7) and .deskthemepack (Windows 8 and later) are CAB archives wrapping a .theme file and its assets, so they are structurally close cousins. The difference is what the newer .theme manifest is allowed to say: the Windows 8 version added the [Slideshow] section for rotating wallpapers and multi-monitor support. A .deskthemepack renamed to .themepack will often apply on Windows 7, but the slideshow and multi-monitor features silently do nothing because the older shell cannot read them. The clean way to produce a genuine Windows 7 pack is to build the theme on Windows 7 and use “Save theme for sharing.”

Frequently asked questions

Why rename to .cab and not .zip?

Because a .deskthemepack is a Microsoft Cabinet archive, not a ZIP. Its first four bytes are MSCF, which a ZIP tool does not recognise, so renaming to .zip makes the file look corrupt. Rename a copy to .cab and open it with File Explorer or 7-Zip, both of which read cabinets.

Can I use a .deskthemepack on a Mac or phone?

No. It is a Windows desktop theme and only Windows 8, 10 or 11 can apply it. What does transfer is the artwork: rename a copy to .cab, extract the wallpaper images (they are ordinary JPG/PNG), and set those as your background on any device.

Why does double-clicking do nothing?

Usually the Windows edition is too old (the pack needs Windows 8 or later) or the .deskthemepack file association has been changed. The file is not necessarily broken; you can still reach the wallpapers and sounds by renaming a copy to .cab and opening the cabinet.

References