Every frame you see in a game is the end product of a strict, ordered sequence: the graphics rendering pipeline. A render pipeline takes the objects in a scene and displays them on-screen, repeating its steps each time a new frame is generated, as Unity's engine documentation puts it. The process moves data through stages—culling, rendering, and post-processing in Unity's framing, or modeling, illumination, viewing, clipping, projection, scan conversion, and visibility in the classic academic formulation—each stage forwarding its result to the next. Understanding that order, and what each stage does to the data, is the key to diagnosing why a game runs smoothly or stutters.

The Graphics Pipeline: A Step-by-Step Data Flow

Here is the full journey of a single triangle, from raw model data to a shaded pixel on screen. Each stage consumes a specific form of data and hands off a transformed version to the next:

The rendering pipeline as a sequence of data transformations
StageWhere it runsInputWhat happens to the dataOutput
Application / ModelingCPUScene objects defined in their own local coordinate systems (object space)CPU prepares the scene, issues draw calls; modeling transforms orient models within a common world coordinate frameScene data in world space, sent to the GPU
Vertex processingGPUVertex attributes (position, normal, texture coordinates) pulled from buffer objectsVertex shader transforms coordinates through model, view, and projection operations; lighting may be computed per vertexVertices positioned for projection; per-vertex values such as color ready for interpolation
Clipping and cullingGPUProjected geometryObjects outside the camera view (frustum culling) or hidden behind others (occlusion culling) are removed; geometry outside the viewable boundary is discarded for efficiencyOnly visible, on-screen geometry
RasterizationGPUTransformed trianglesContinuous primitives are converted into discrete fragments, each corresponding to one pixel of the screen; edge equations interpolate colors and other per-vertex data across the pixels the triangle touchesA grid of fragments with interpolated attribute values
Fragment processingGPUInterpolated fragment data, textures, lighting parametersA fragment shader calculates the final RGBA color at each sample position; depth testing and alpha blending resolve overlaps and transparencyFinal per-pixel color and transparency values
Output merging / post-processingGPUCompleted pixel buffersPipeline modifies the buffers to generate the final frame—color grading, bloom, depth of fieldThe frame sent to the display

The crucial insight the table encodes: the pipeline is not a single operation but a relay. Each stage exists to prepare the data for the specific job of the next, and a frame is only as fast as its slowest link.