Why a Screen Needs a Hidden Second Image
A game frame is assembled through many operations: drawing backgrounds, characters, effects, and interface elements. If those changes are sent straight to the visible screen, the display can catch the image halfway through the process. The result may look torn or partly updated—not because the game has drawn the wrong scene, but because the screen has shown two stages of the same frame at once.
Double buffering gives the renderer a private workspace. The back buffer is an image-sized memory area that the game can change without exposing those unfinished updates. Meanwhile, the display continues showing the completed image in the front buffer.
The Swap Is the Handoff
Once the new image is ready, the system switches which buffer the display reads. That handoff is called a buffer swap or page flip. The old front buffer becomes available for drawing the following frame, while the newly completed one is presented as a whole.
Timing matters: a swap made while the display is scanning across the screen can still produce a visible boundary between frames. Systems therefore commonly coordinate presentation with the display’s refresh cycle, so the change happens at a suitable moment. This helps avoid tearing, though it does not guarantee that every frame arrives on time.
Smoothness Has a Cost
Keeping a separate image takes memory, and preparing a frame still takes time. Double buffering hides incomplete drawing; it does not make the rendering work disappear. If a game cannot finish a frame before its presentation opportunity, the display may keep showing the previous image or the game may feel less responsive, depending on how presentation is managed.
The key design tradeoff is visibility versus timing: the player gets a coherent image, while the renderer works out of sight. What looks like one instantaneous picture is actually a completed image handed to the screen at the right moment.
