QUICKUPSCALE

BROWSER-LOCAL · ORDERED PNG FRAMES

Sprite sheet maker

Order PNG frames, choose a grid, strip or column and download one sprite sheet. No account or image upload.

Or drop PNG frames here. Images stay on this device.

1–32 static PNGs, 10 MiB each and 64 MiB combined. Output dimensions and browser memory limits also apply. Animated PNGs are rejected.

0 PNG frames selected

Frame order
    Sheet layout

    Blank cells at the end stay transparent. Frame pixels keep their original size.

    Frame size policy
    Padding anchor

    Choose order before layout

    Natural order compares numeric filename runs, so frame-2 precedes frame-10. Matching normalized names retain selection order. Switch to manual order and move the visible source IDs when filenames do not describe the intended sequence. The manifest keeps both the source index and the placed frame index.

    A grid fills rows using your column count. A horizontal strip uses one row; a vertical column uses one column. Any unused cells at the end remain transparent. This tool arranges frames without resizing, rotating, trimming or bin packing.

    The frame-order walkthrough follows an explicit eight-frame sequence through case and Unicode filename collisions.

    Equal dimensions or explicit transparent padding

    Equal-size mode rejects a selection whose frame dimensions differ. Padding mode uses the largest frame width and height as its cell size. Top-left alignment keeps the original origin; centered alignment divides spare space around the frame, placing an odd extra pixel on the right or bottom. Check the manifest's content and allocated rectangles before importing.

    One PNG download contains the complete sheet. Its ZIP includes the identical PNG and a manifest with top-left, half-open rectangles, original dimensions and padding offsets. The small result preview is physically limited to 128 pixels per edge. It is not a full-resolution inspection of every frame.

    Prepare frames and keep source metadata

    Use the sprite sheet splitter to extract a regular source grid first. For larger frame pixels, run the frames through the batch PNG upscaler before assembling. The maker's JSON is a geometry manifest, not an engine atlas format; it does not recreate animation tags, timing or import settings.

    Static PNG and atomic export limits

    Select 1–32 static PNGs, up to 10 MiB per file and 64 MiB combined. Animated PNGs and corrupt files are rejected. Both source and output geometry must fit 16,777,216 pixels and 16,384 pixels per edge. A separate conservative memory estimate can reject smaller selections. One invalid source fails the whole assembly; cancellation and archive errors publish no partial sheet.

    Image decoding and PNG encoding require browser worker support. Browser canvas conversion can round partial-alpha colors, discard invisible RGB and omit source PNG metadata. Keep your originals and their animation sidecars. The transparent-edge guide explains that codec boundary.

    ? QUESTIONS

    Does the maker resize my frames?
    No. Equal-size mode requires matching dimensions. Padding mode keeps each frame at its original pixel size inside the largest cell, anchored at the top left or centered.
    How do I control animation frame order?
    Natural filename order compares numeric runs so frame-2 precedes frame-10. Manual order uses the visible move controls and source IDs. The manifest records source indices and placed frame rectangles; it does not add animation timing or tags.
    What are the input and preview limits?
    Choose 1–32 static PNGs, up to 10 MiB each and 64 MiB combined. Animated PNGs are rejected. Geometry and a conservative memory budget also apply. The physical result preview is at most 128 pixels per edge; download the full PNG for import.