How to import and slice a sprite sheet in Unity

Drop the PNG into Assets/ and select it. In the Inspector, Texture Type has to be Sprite (2D and UI). A project made from the 2D template does this for you; one made from the 3D template imports PNGs as plain textures, which is why the sheet cannot be dragged into the scene and every tutorial step stops matching.

Then Sprite Mode → Multiple. This is the whole difference between "one sprite that happens to be a grid of characters" and "a container of sub-sprites". Left on Single, the Sprite Editor opens but has nothing to slice, and the frames never appear as separate assets.

Press Apply. The import panel does not commit anything until you do, and it is easy to change five settings, open the Sprite Editor and wonder why none of them took.

If the Sprite Editor button is missing entirely, the 2D Sprite package is not installed — Window → Package Manager → Unity Registry. It ships with the 2D templates and not always with the others.

Unity's defaults are tuned for photographic textures in a 3D game. Every one of them is wrong for a 32×32 sprite, and none of them announce themselves.

Click Sprite Editor. The Slice dropdown is top-left, and its Type field offers three ways to describe the sheet:

The pivot is the sprite's origin: the point that sits at the transform's position. It defaults to Center, and for a character that is almost never what you want — Bottom puts the origin at the feet, so placing the character on the ground is setting y to the ground's y, and a taller frame in the attack animation grows upward instead of sinking into the floor.

Set it in the Slice dropdown so every frame gets it at once. Individual frames can be overridden by selecting them in the Sprite Editor, and a Custom pivot is specified in normalised coordinates — 0,0 is bottom-left, 1,1 is top-right.

Inconsistent pivots are the cause of the classic "the character jitters while walking" bug. Nothing is wrong with the animation; frame 3 just has its origin a pixel off, so the whole sprite hops. Automatic slicing is the usual culprit, because it fits each rect to that frame's own pixels and a frame where the arm swings wider gets a wider box.

Expand the texture's foldout arrow in the Project window — the sub-sprites are in there. Select the frames of one animation in order, drag them into the Scene view, and Unity creates a GameObject, an Animator Controller and an Animation Clip in one go, prompting for a filename.

Dragging onto an existing GameObject that already has an Animator adds a clip instead of creating everything again, which is what you want for the second and third animations of the same character.

Then fix the speed. The generated clip has a sample rate that has nothing to do with your art, and pixel art animation usually wants 8–12 fps. The field is Samples in the Animation window — and in current Unity versions it is hidden until you turn on Show Sample Rate in that window's gear menu, which is why plenty of people conclude the field was removed and go looking for a speed multiplier on the Animator state instead.

Deciding the rate before you are in the editor saves the round trip. The Sprite Animation Previewer plays a sheet back at any FPS in the browser, so you can find the number that reads right and then type it once.

Point filtering keeps the texture sharp. It does nothing about the camera rendering the world at a fractional scale, which makes some pixels two screen pixels wide and their neighbours three — the sprite crawls and shimmers as it moves, and it is worse in motion than any still screenshot suggests.

Add the Pixel Perfect Camera component to your camera (part of the 2D Pixel Perfect package, bundled with URP's 2D renderer). Set Assets Pixels Per Unit to the same number you used in the import settings — a mismatch here undoes the whole point — and a Reference Resolution matching your intended internal resolution, such as 320×180 or 640×360.

Upscale Render Texture renders the game to an offscreen target at the reference resolution and scales that up as a block, which removes sub-pixel movement entirely; it also means smooth camera motion becomes stepped, which some games want and some do not. Pixel Snapping is the lighter option: sprites snap to a grid, the camera moves freely.

If the art you inherited was already upscaled — a 16×16 sprite saved at 64×64 — none of this helps until it is back at native resolution, because Unity is now scaling an already-scaled image. The Pixel Art Resizer detects the factor and reverses it.

Unity's slicer is good enough that this is a narrower list than for other engines. It still has three real limits.

Automatic slicing guesses, and guesses badly at the edges. Two frames whose pixels touch become one rect. A frame with a detached element — a sword glint, a dust puff, a floating hat — becomes two. Neither is reported; you find out when the animation is wrong. On a sheet with these, the Sprite Sheet Cutter gives you the same detection with a merge distance you control, plus a grid mode and a visible per-frame result before you commit.

Sub-sprites are not files. They exist inside the texture asset. The moment something outside Unity needs one frame — a store page, an icon, a UI mockup, a bug report, a second project on a different engine — there is nothing to hand over. Individual PNGs are portable in a way sliced rects are not.

Re-slicing can break clips. Slicing with Delete Existing recreates the sub-assets, and animation clips referencing the old ones can end up pointing at nothing — a working animation that suddenly renders blank after the artist sent an updated sheet. Individual PNG files replaced in place never have this failure mode, which is a reason some teams keep frames as files even though Unity could slice them.

For the common case — a clean grid from your own art tool — slice it in Unity and ignore all of this.