Foundry VTT WebM Token Performance Guide
Keep Foundry animated tokens practical with 512p choices, selective animation, PNG fallbacks, package organization, and scene testing.
Quick Answer
Keep Foundry animated tokens practical with 512p choices, selective animation, PNG fallbacks, package organization, and scene testing.
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
Treat animation as a scene budget.
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
Use 512p for normal tactical play and larger exports for showcase use.
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
Keep WebM files, PNG fallbacks, thumbnails, and import notes together.
Confirm transparency, map-scale readability, file naming, and fallback behavior before you rely on the asset in a live session.
Workflow Checklist
- Treat animation as a scene budget.
- Use 512p for normal tactical play and larger exports for showcase use.
- Keep WebM files, PNG fallbacks, thumbnails, and import notes together.
FAQ
What is Foundry VTT WebM Token Performance Guide 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.