Creator guide
Documentation
Learn how to create cleaner prompts, generate consistent animation assets, and export spritesheets for your game engine.
Last updated: March 1, 2026
Generate animation-ready sprite assets from a prompt and optional reference image.
Export transparent spritesheets with consistent frame sizing for game engines.
Review, download, share, and reuse completed generations from your history.
Recommended Workflow
Start broad, then tighten the result. The best sprites usually come from a clear reference, a single animation goal, and one or two refinement passes rather than an overloaded first prompt.
Choose one animation goal: idle, walk, run, jump, attack, cast, hurt, or another simple loop.
Upload a clean character reference when you need consistent colors, costume details, proportions, or silhouette.
Write a focused prompt with character, action, camera angle, style, frame count, and background preference.
Preview the output, download the spritesheet, then test timing and frame slicing inside your engine.
Prompt Guide
Good prompts describe one character, one action, one camera angle, and one visual style. For example: "small pixel art knight, side view, 8-frame sword slash, readable silhouette, transparent background." Avoid mixing too many actions or camera directions in a single prompt.
Prompt example
small pixel art knight in blue armor, side view, 8-frame sword slash animation, readable silhouette, consistent proportions, transparent background
- Describe the character's shape, outfit, weapon, colors, and animation action
- Name the art style, such as pixel art, clean cartoon, anime, painterly, or hand-drawn
- Specify the camera angle and orientation, such as side view, front view, or top-down
- Ask for a transparent or simple background when the output is meant for game sprites
- Keep the animation to one readable motion; split complex combos into separate generations
- Use words like loopable, readable silhouette, consistent scale, and centered character when useful
Reference Images
Reference images help preserve character design, palette, pose language, and silhouette. Use a single clear subject with minimal background clutter. Images with strong lighting, cropped limbs, heavy perspective, or multiple characters can reduce consistency.
- Use one character per image, ideally full body or clearly framed from the angle you want
- Avoid screenshots with busy backgrounds, motion blur, UI overlays, or multiple poses
- For pixel art, upload crisp references and mention pixel art explicitly in the prompt
- If a detail is important, describe it in the prompt even when it appears in the reference
Spritesheet Output
Generated spritesheets are exported as transparent PNG files arranged in a horizontal strip with equally sized frames. You can also review previews and related assets from the generation detail page. For best in-engine results, keep frame dimensions consistent across animations for the same character.
- Use the same frame size and origin point across a character's idle, walk, run, and attack animations
- Test playback speed in your engine; a good spritesheet may still need timing adjustment
- Keep a naming convention such as character_action_framesize_frames for easier imports
- Download and archive final assets before deleting generations or rotating project files
Game Engine Integration
The exported PNG is designed to work with common 2D workflows. After import, slice the horizontal strip into equal frames, set the origin point, adjust playback speed, and verify collision masks separately from the visual sprite.
Unity Integration
Import the PNG, set Texture Type to Sprite, choose Multiple mode, and slice by grid or frame count in the Sprite Editor. Then create an Animation Clip from the sliced sprites and adjust samples per second to tune playback speed.
Godot Integration
Import the PNG and use AnimatedSprite2D with a SpriteFrames resource, or use Sprite2D with an AnimationPlayer. Set the horizontal frame count to match the spritesheet and keep filtering disabled for crisp pixel art.
GameMaker Integration
Import the PNG as a Sprite resource and set the number of sub-images to match the frame count. Confirm the origin point, collision mask, and playback speed before using the sprite in objects or state machines.
Credits System
Generations and related processing actions consume credits. Signup bonuses, daily bonuses, purchases, and subscriptions may grant credits depending on current account settings. If a generation fails due to a service error, credits may be refunded automatically; subjective output quality, prompt experimentation, or normal completed generations generally still consume credits.
- Check the button label before generating; it shows the current credit cost for that action
- Failed service-side generations may be refunded automatically when the backend marks them failed
- Purchased credits and subscriptions are governed by the Terms of Service refund policy
Shared previews are useful for feedback, client approval, and portfolio snippets, but they should not be used for assets that are confidential, unreleased, or licensed under terms that restrict public display.
Troubleshooting Better Results
AI output can vary. When a result is close but not production-ready, small prompt changes usually work better than rewriting everything from scratch.
- If the character changes too much, simplify the action and strengthen the reference image
- If motion is unclear, reduce the animation to one verb like walk, jump, slash, cast, or idle
- If frames feel noisy, ask for a cleaner style, simpler shapes, and a readable silhouette
- If imports look blurry, disable texture filtering or compression settings in your game engine
API Access
API access is intended for teams that need programmatic generation, pipeline integration, or higher-volume workflows. Contact us with your use case, expected volume, and integration needs so we can recommend the right setup.