HelpFormat

Animated PFP collections

Same as standard PFP but with animated GIF traits. Each output is an animated GIF. Capped at 1,500 works because the encoder is far heavier per token than the static path.

What it is

An animated PFP collection ships works with motion - blinking eyes, swaying hair, flashing backgrounds. Each layer can hold animated GIF traits in addition to (or instead of) static PNGs, and every output is an animated GIF that loops in marketplaces / wallets that support it.

Why a separate type

Encoding an animated GIF is dramatically heavier than a static PNG: the compositor decodes every frame of every picked GIF trait, blends them, palette-quantizes the result and re-encodes the full loop. We cap the edition at 1,500 works to keep that load inside what a typical browser can finish without crashing. Static PFP collections stay at the 10,000 cap.

How you build one

Pick the 'PFP collection' card on /create, then flip the Static/Animated toggle inside the editor's Edition step. The editor accepts both GIF and static traits per layer. Use the per-trait compressor to cap each GIF's frame count + dimensions (16 frames / 600 px is a good sweet spot for sub-200 KB output). Preview live, validate, deploy - same flow as standard PFP.

Caps and constraints

Edition cap: 1,500 works. Render size: up to 1000×1000 (same picker as static PFP), but 600×600 stays the safe default for animated — each token at 1000 px does ~2.8× the pixel work AND ships a multi-frame GIF, so the full-collection preview can chew 8-10 GB of RAM at the 1500-cap. Output format: animated GIF for every token, even ones where every picked trait happens to be static (uniform extension keeps wallet thumbnails consistent).

Need a personalised answer?

ChatZilla lives at the top of the Help center. It knows every topic in this center and can walk you through your specific collection, wallet or transaction.

Create