UI Crafter for Aseprite

Workflow

Limitations

Known constraints around experimental effects, Aseprite dialogs, text, transforms, and external layout tools.

Limitations and beta notes

Beta releasePixMold is usable today, but some workflows, examples, and advanced effects are still being refined from real project feedback.

PixMold is currently released as a beta. The core workflow is usable, but some parts of the tool, documentation, and examples are still being improved.

The goal of this beta is to make PixMold available to real users, collect feedback, and refine the workflows that matter most in practice.

Not a replacement for hand-made UI art

PixMold is designed to help with iteration, structure, and reusable UI generation.

It can help you create buttons, panels, slots, frames, materials, states, previews, and sprite-sheet-ready outputs faster, but it is not meant to replace final artistic direction.

For best results, use PixMold as a UI construction and experimentation tool, then polish, redraw, or customize the result when your project needs a more specific hand-crafted style.

Large projects can become slower

PixMold uses Aseprite scripting and renders editable UI elements through layers, effects, previews, and project data.

Very large elements, many states, heavy effect stacks, large preview templates, or big sprite-sheet renders may take longer to update or draw.

For smoother work:

  • keep early experiments small;
  • duplicate complex elements only when needed;
  • save regularly;
  • render large outputs after the design is mostly stable;
  • split very different UI sets into separate PixMold projects if needed.

Some workflows are still being polished

PixMold already includes many tools, but some advanced workflows may still change or improve during the beta.

This includes areas such as:

  • advanced source-layer workflows;
  • complex effect combinations;
  • import and resource-management edge cases;
  • preview layout comfort;
  • large render workflows;
  • documentation coverage;
  • starter-pack examples.

Project files created during the beta are intended to remain useful, but some settings, templates, or workflows may be adjusted as the tool evolves.

Text effects are experimental

PixMold includes a basic text effect mainly for quick placeholders and visual testing.

It is useful when you need temporary labels while adjusting a panel, button, or preview layout, but it is not intended to replace proper text work.

For production UI text, the recommended workflow is still to use Aseprite text layers, converted shapes, or your game engine’s native text rendering when appropriate.

Starter packs are examples, not fixed art packs

Included starter packs are editable examples and workflow starting points.

They are meant to show how PixMold projects, elements, states, layers, effects, materials, and preview layouts can be organized.

You can use them, modify them, recolor them, and reshape them for your own projects, but they should not be treated as a complete final UI style library.

Save before destructive actions

PixMold manages editable project data inside Aseprite, but some operations can significantly change your current setup.

Before importing, resetting, closing, duplicating large structures, or experimenting heavily with effects, save your project.

When testing a risky variation, it is often safer to duplicate the element, duplicate the state, or save a separate project version first.

Feedback is welcome

PixMold is being released now because it is more useful to improve it with real user feedback than to keep polishing it alone.

If you find a bug, confusing workflow, missing documentation, or an effect that does not behave as expected, please report it with:

  • your PixMold version;
  • your Aseprite version;
  • what you were trying to do;
  • what happened;
  • whether the issue happens again after reopening the project;
  • a screenshot or small project file if possible.

The beta will improve around the workflows people actually use.