Desktop composition combines the visual surfaces produced by applications into the image presented on a screen. It lets the operating system manage overlapping windows, effects, and presentation without each program drawing directly over every other one.
How the pieces connect
Applications render into surfaces that the compositor can arrange and combine. Timing coordinates when a completed image becomes available for presentation. The rendering process, composition process, and display scanout can involve different queues and resources. A smooth-looking desktop depends on their cooperation, not solely on the speed of one application's drawing commands.
An everyday example
Moving a translucent window over another application does not require the underlying program to understand the entire desktop layout. The compositor can combine their surfaces according to the current arrangement. A video player may use a different presentation path from a static document window while still appearing within the same overall desktop.
Reading the information in context
A visible pause can arise at several stages, so observation alone does not isolate a single graphics component. Refresh timing, application work, and system scheduling all contribute. This page is not a diagnosis of a particular display experience. It explains why rendering and presenting are separate activities and why a single utilization percentage cannot describe the complete visual path.
Display & Graphics
Note these before you change anything
Useful facts to have to hand while reading about desktop composition and surfaces.
- Current driver version and date from the adapter's Driver tab
- Resolution, refresh rate and scaling for each monitor
- Which port and cable each display uses
- Any per-application graphics settings you changed
Display & Graphics: Drawing a frame (output)
- Applicationrequests drawing
- Graphics APIfor example DirectX or Vulkan
- Display driveruser and kernel parts
- GPUrenders the frame
- Monitorover the display cable
