An Animated Sticker-Pack Workflow

Animated sticker packs occupy a unique production niche. They are small enough in file size that they must be heavily compressed, yet they must maintain visual clarity and readable character expression at the small display sizes messaging apps use — typically 100 to 200 pixels at display resolution on a phone screen. Animation must loop perfectly with no visible stutter or discontinuity at the loop point, because a poorly looping sticker becomes irritating to look at rather than delightful. And most importantly, every sticker in the pack must read as part of the same character family — same face, same proportions, same art style — even though each depicts a different emotion or action.

Marketplace technical requirements add another layer of complexity. Apple iMessage stickers require APNG format, 206x206 to 618x618 pixels at 3x. WhatsApp sticker packs require WebP at 512x512 pixels. Telegram supports WebP animated stickers. Line stickers require PNG for static and APNG for animated, at 370x320 pixels with specific frame count and duration constraints. Each platform has a different format, different pixel dimension, different maximum file size, and different animation duration limit. A complete multi-platform sticker pack requires format conversion and validation for each platform before submission.

The Floniks animated sticker-pack workflow handles the entire production pipeline: starting from a character design sheet, generating static sticker frames at consistent character proportions, converting the static frames to smooth animation sequences, engineering clean loop points, converting to all required delivery formats, validating against per-platform technical constraints, and producing the metadata files required for marketplace submission.

The workflow starts with a Character Sheet node that accepts the sticker character design — a clean illustration showing the character at neutral expression in front view, along with any color palette notes or characteristic design elements that must appear consistently across all stickers. The character sheet is the identity anchor for the entire pack; all sticker frame generation downstream is conditioned on it.

A Sticker Pack Brief node defines the pack content: a list of sticker concepts, each described by a short emotional or action label (happy, laughing, crying, thumbs up, thinking, sleeping, waving, heart eyes, and so on), the target platforms, and the desired animation style per sticker (bounce, wave, wiggle, pulse, or custom). The brief also specifies the art style if it needs to be different from the raw character sheet style — a character designed as a pencil sketch might be interpreted as flat illustration for the sticker pack, requiring an art style instruction in the brief.

The Character Sheet and Sticker Pack Brief together feed a Sticker Concept Expander node that, for each concept in the brief, generates a text description of the static keyframe pose: "character with wide open smile, eyes curved upward in crescent shape, both arms raised in celebration, slight lean backward, confetti elements floating around character." These pose descriptions are used in the per-sticker generation prompts alongside the character sheet conditioning, ensuring both character identity and concept-specific pose are enforced simultaneously.

For each sticker concept, a Static Frame Generation node receives the expanded pose description, conditions on the character sheet image at strength 0.55, and generates the sticker keyframe at 512x512 pixels with a transparent background. The transparent background (alpha channel) is critical — stickers must composite cleanly over any chat background color, and any background fill will look wrong in certain chat themes. The generation prompt explicitly enforces background transparency: "character on transparent background, no background elements, no drop shadow extending into background, clean outline defining character edge."

After reviewing and approving the static frames for all sticker concepts, the Animation Conversion chain begins. Each approved static frame routes to an Animation Frame Expander that generates four to eight additional frames representing the motion arc of the animation concept. For a bounce animation, the expander generates frames showing the character slightly compressed at the bounce nadir and slightly stretched at the peak; for a wave animation, it generates frames showing the hand in different wave positions; for a wiggle, it generates frames showing slight rotational wobble.

Frame generation uses the original static frame as a strong conditioning anchor (strength 0.2 to 0.3) to ensure character identity is maintained across all animation frames — only the specific moving elements should change between frames. The frames are assembled into an animation sequence by an Animation Composer node that determines frame timing. A standard sticker animation runs at 12 frames per second for a smooth but bandwidth-conservative result. The Animation Composer also engineers the loop point: the final frame must transition cleanly back to the first frame without a visible jump, which requires that the animation arc ends in the same or a visually equivalent pose to the starting frame.

After animation sequences are composed, each sticker passes through a Platform Conversion chain that produces the required format for each target platform. A conversion router reads the target platforms from the Sticker Pack Brief and activates only the conversion branches needed for this pack.

For iMessage APNG conversion, the animation frames are assembled into an APNG file at the required iMessage dimensions. The maximum file size for an iMessage sticker is 500KB; the APNG compression settings are tuned to stay within this limit while maintaining visual quality. A validation node checks the output dimensions (must be between 206x206 and 618x618 pixels), the file size (must be under 500KB), and the frame count (must be between 2 and 24 frames for animated stickers).

For WhatsApp WebP conversion, the frames are assembled into an animated WebP at 512x512 pixels. WhatsApp enforces a strict 500KB file size limit and a maximum duration of 3 seconds per sticker. The conversion node checks duration against the frame count and frame rate, and the validation node confirms all constraints are met. For Telegram animated stickers, the target format is WebM (VP9) at 512x512 at 30 fps. For Line, the target is APNG at 370x320 with constraints on frame count (4 to 8 frames for animated stickers).

A Validation Report node at the end of the conversion chain produces a per-sticker, per-platform validation table: each sticker name, each platform, dimensions, file size, duration, and pass or fail status. Failed validations are flagged with the specific constraint that was not met and the recommended fix. Only stickers that pass all target-platform validations proceed to the final export package.

After all stickers have passed platform validation, the Pack Assembler node organizes the outputs into a submission-ready package structure. Each platform requires a different folder and file organization. The iMessage pack requires an Xcode-compatible asset catalog structure with each sticker as a named APNG file in a Stickers folder. The WhatsApp pack requires a folder of WebP files accompanied by a tray icon (96x96 PNG representing the pack) and an Android metadata JSON file specifying the pack name, publisher, and licensing terms. The Telegram pack requires a ZIP archive with specific naming conventions.

A Metadata Generator node produces all required metadata files. It draws the pack name, publisher name, and description from the Sticker Pack Brief and writes them into the format-specific metadata file for each platform. For marketplace submissions (iMessage App Store, LINE Store, WhatsApp sticker API), the metadata must include specific fields — content rating, primary language, keyword tags for discovery — that are also stored in the Sticker Pack Brief and written by the Metadata Generator.

The tray icon — the small thumbnail that represents the pack in the sticker picker UI — is generated by a Tray Icon node that composites two or three of the most expressive stickers from the pack into a collage at the required tray icon dimensions. This ensures the tray icon represents the actual pack content rather than being a generic placeholder. Export the complete pack to a folder named "[character-name]-sticker-pack-v1/" containing a subfolder for each platform. Save the workflow as "StickerPack-[Character]-v1" for reuse when new sticker concepts are added to the pack or when the pack is updated with new animation styles.