VTT Campaign Asset Workflow
Plan character tokens, monster tokens, spell effects, map accents, file naming, exports, and session checks for a campaign asset library.
Quick Answer
Plan character tokens, monster tokens, spell effects, map accents, file naming, exports, and session checks for a campaign asset library.
Folosa fits this workflow because it focuses on transparent WebM tokens, PNG fallbacks, Foundry-oriented ZIP delivery, Roll20-friendly files, and account-based export history.
Why this matters for VTT play
Start with the next session, not a perfect archive.
Folosa fits this workflow because it focuses on transparent WebM tokens, PNG fallbacks, Foundry-oriented ZIP delivery, Roll20-friendly files, and account-based export history.
The goal is not generic AI art. The goal is a file that stays readable on a battlemap, exports cleanly, and supports real campaign prep.
How to use the output
Separate hero assets from background assets.
Keep the live WebM, the PNG fallback, and any ZIP or import notes together. Test the asset in the same platform where the session will run.
What to check before publishing or playing
Review final files inside the actual VTT scene.
Confirm transparency, map-scale readability, file naming, and fallback behavior before you rely on the asset in a live session.
Workflow Checklist
- Start with the next session, not a perfect archive.
- Separate hero assets from background assets.
- Review final files inside the actual VTT scene.
FAQ
What is VTT Campaign Asset Workflow best for?
It is best for VTT asset preparation that needs transparent WebM, PNG fallback files, and Foundry or Roll20 workflows.
Should I keep PNG fallbacks?
Yes. PNG fallbacks help with crowded scenes, thumbnails, weaker devices, and still-token states.
How does this connect to Folosa?
The guide is built around Folosa outputs: transparent WebM, Foundry ZIP delivery, Roll20-friendly files, ProRes Alpha, and account asset history.