A sprite sheet is one image that packs many sprites, or many frames of one sprite, into a grid so a game can draw them from a single texture. The engine does not load a file per frame. It shows a rectangle of this image, then the next rectangle, at the rate the animation asks for.
How a Sprite Sheet Works
The picture is a texture. The meaning is the grid.
Cells are the same size, or each frame records its own rectangle when the packing is tighter than a uniform grid. A margin keeps the cells off the image edge. Spacing keeps neighbors from bleeding into each other when the texture is filtered. Play order is reading order unless the sheet says otherwise: left to right, then top to bottom. Empty cells are skipped, so a frame index can jump.
One sheet often holds more than one animation. A character might keep idle, walk, and attack on the same texture, each animation a list of frame indexes rather than a separate file. Drawing from one texture is why sheets exist: a GPU binds the image once, and the game only changes which rectangle it samples.
Frames and Animation
A frame is one pose. An animation is an ordered list of frames, a frame rate, and a loop flag.
The frames have to agree before the list is worth playing. If the feet land on a different pixel each cell, the character slides. If the scale drifts, the body pulses. If the anchor, the point the engine places the sprite by, is not shared, the figure hops. Building the frames as one sheet is how those three stay locked. Cutting them from separate generations and hoping they line up is how they do not.
A loop plays the list and returns to the first frame. A one-shot, such as an attack, plays the list and holds the last frame. Both are data on the animation, not a property of the PNG.
Formats and Metadata
The image is usually a PNG. Transparency matters, because a sprite that brings its own background cannot sit on a level. Some pipelines use a color key instead of an alpha channel. Either way, the picture is only half the file.
The other half is the cut list. A uniform grid can be described with columns, rows, cell width, cell height, margin, and spacing. A packed atlas needs a rectangle per sprite, because the cells are not equal. Each frame can also carry an anchor, the point it stands on, so a tall frame and a short frame share a ground line. Named animations then point at frame indexes, with a frame rate and a loop.
Without that record, someone measures the sheet by hand in the engine. With it, the importer slices the texture the same way every time. Unity's sprite editor, Godot, GameMaker, and Unreal's Paper2D all consume a PNG plus some version of this cut list. The names differ. The job does not.
How Engines Use a Sheet
The typical import is: drop in the PNG, set the sprite mode to multiple, and either slice by cell size or read the atlas data. The game then plays an animation by swapping the rectangle, not by swapping files. A workflow that emits the PNG and the cut list together is what keeps a content update from becoming an afternoon of manual slicing.
Pixel art sheets add one more constraint. Every cell has to sit on the same pixel grid, in the same palette, or the animation shimmers. That is a property of how the frames were drawn, which a packer cannot invent after the fact.
How Layer Builds a Sprite Sheet
Describe the subject and the motion, such as a six-frame walk read left to right, and Layer's sprite sheet tool lays those frames on one image. You can also start from a picture you already have and turn it into a sheet of views or poses. The sprite sheet tool is that job. Sprite generation is the wider one, including walk cycles that share scale, ground line, and anchor.
For pixel art, name the machine or paste a hex palette in the prompt, then check the sheet's colors before you use it. The snap described in image to pixel art and pixel art for real hardware can apply a declared palette to one sprite. It is not suited to a multi-frame strip, which is drawn per frame rather than on one grid. Ask for a transparent background when the frames should composite.
You can split a finished sheet into frame files, or pack loose frames into one uniform sheet. Both are file operations and spend no Creative Units. Packing records the grid and each frame's rectangle on the file, and an anchor when the frames share one. The metadata format also supports named animations, with frame indexes, a frame rate, and a loop. An empty animation list means the whole sheet plays as one loop. Generating a sheet does not write that record by itself.
Style training keeps a cast of sheets in one rendering when the game is not locked to a hardware palette. The sheet is still the same object: one image, a grid, and the list of frames an engine plays.