Plan asset handoffs, check sprite and texture data, profile representative scenes and retain source files, import settings and acceptance evidence.
List each asset’s role, source owner, license, target platforms and acceptance conditions. Specify dimensions or scale, orientation, naming, animation requirements and required source files. Use a representative scene to judge readability and style before producing the entire set.
Record the pixel dimensions after export or import. Use pixel count to compare a proposed resolution with an explicit reference; use an exact aspect ratio when matching a UI frame. For a regular sprite sheet, verify equal whole-pixel cells from its sheet size, columns and rows. Configure margins, pivots and extrusion in the art or engine tool.
Inspect the imported format on every target. Enter the actual dimensions, format, mip selection and identical face or layer count to compare texture data sizes. Check whether the target graphics API permits the chosen format and dimensions, and inspect small mip levels for artifacts. Treat a mathematical footprint as one part of the resource record.
Test the imported assets in scenes that exercise their real materials, lighting, transparency and animation. For particle buffers, enter allocated capacity, measured bytes per entry, copies and fixed overhead to describe only that data allocation. Capture actual render timings, overdraw and memory residency on the target hardware before changing quality settings.
Check dimensions, orientation, color, alpha edges, animation pivots and transitions in the built game. Generate named target/configuration/test cases for the handoff and record failures with asset identifiers. Measure real build components if estimating packaging; enter a factor derived from a comparable build and explicit overhead, then compare the estimate with the final artifact.
Deliver editable source files, final exports, import settings, license records and the acceptance evidence together. Name the approved revision and unresolved issues, with an owner for each next action. Re-export one changed asset from the instructions and confirm it replaces the intended resource without breaking references.
Draft and download the asset brief and reproducible export record.
Compare actual pixel counts with a chosen reference resolution.
Calculate the exact ratio of an exported rectangle.
Validate equal unpadded sprite-grid cells.
Count imported texture data across the chosen mip levels and layers.
Count a measured particle buffer layout and explicit copies.
Record asset acceptance across named builds and configurations.
Estimate packaging from measured component sizes and explicit assumptions.
Loading your checklist…
Microsoft documents whole compression blocks and the treatment of small mip levels. The calculator models block-rounded data; verify resource-creation restrictions in the API you actually use.
Unity’s target-platform profiling workflow provides performance evidence from the built application. Retain the build and capture conditions alongside your asset comparison.
Use one row or linked record per asset revision.
| Record | Details |
|---|---|
| Identity | Asset ID, source revision, owner and license |
| Import | Target override, dimensions, format, mips and layers |
| Visual check | Scene, device, capture and observed artifact |
| Handoff | Reproduction steps, approved revision and remaining issue |
Validate one asset through the full pipeline before producing a large batch.
MiB describes bytes in powers of two. Separate data footprint, file size and runtime allocation.