Website Forge
Use Build, Prompt, or Upload in your browser. This is the quickest way to create, preview, download, and reuse a token.
Complete Folosa guide: website, Bridge, and manual delivery.
Start with the website Forge for the simplest path. Use Folosa Bridge when you want a completed task imported into Foundry as an Actor. The same account owns credits, task history, and downloads in both places.
Choose the path that matches your table.
These pages are related, but they are not duplicate instructions. This page covers the whole journey; the Bridge guide and platform guides go deeper after generation.
Folosa Bridge
Create from Foundry or import an existing completed website task. Bridge uses the same Folosa account and can create a Foundry Actor automatically.
Manual delivery
Download the ZIP from your workspace or account, then use its WebM, PNG, README, and import notes without installing Bridge.
Create one task from one input mode.
Sign in first, choose exactly one mode, then confirm the platform, quality, and visible credit cost. Leaving text in another inactive mode does not combine it with the task.
1. Sign in
Use the account that should own the credits, task history, downloads, and support record. Verified new accounts include 160 free credits.
2. Choose Build, Prompt, or Upload
Build uses guided fields. Prompt accepts a direct character brief. Upload uses your permitted reference image and an optional motion request.
3. Keep the request focused
Describe one subject, its visible equipment, and one readable action. Avoid conflicting anatomy, camera, style, or background instructions.
4. Choose platform and quality
Select Foundry, Roll20, or All. Standard costs 80 CRD, HD Pro 200 CRD, and 4K Master 280 CRD per token.
5. Review before submitting
Confirm the active mode, source image or prompt, quality, and cost. Submit once; do not create a duplicate because a render is taking several minutes.
6. Continue other work
Rendering runs on the server. You can leave the page and return to the workspace or account history later.
Build
Best when you want guidance. Choose lineage, role, setting, and action; Folosa assembles the generation brief.
Prompt
Best when you already know the design. State one character, silhouette, equipment, action, and visual style in plain language.
Upload
Best when identity must follow existing art. The motion field is optional; when blank, Folosa records and uses a safe default movement request.
Prepare upload art for identity and motion.
Upload quality has a direct effect on what the video model can preserve. Folosa validates the file and prepares a safe static input, but it cannot reconstruct important details that are already missing from the source.
| Check | Use | Avoid |
|---|---|---|
| File | PNG, JPG, or WebP; at least 300x300 px; no more than 10 MB. | Corrupted files, screenshots with browser chrome, or images you do not have permission to use. |
| Subject | One clear subject with face, body, limbs, weapons, wings, tail, and effects visible when they matter. | Cut-off anatomy, overlapping characters, collages, or a tiny subject in a large scene. |
| Space | Leave visible room around moving parts. A centered full or medium-full composition is the most reliable. | Hands, weapons, hair, wings, or effects already touching the source edge. |
| Background | A simple or removable background with strong subject separation. | Text, watermarks, UI, dense scenery, or colors that merge with the subject. |
| Motion request | Describe motion using parts already visible, such as raising the existing sword or shifting into a guarded stance. | Adding a new weapon, new costume, new limbs, or several unrelated actions in one request. |
Read the task status before taking another action.
The task list is the source of truth. Credits are reserved when a task is accepted and captured only after a successful delivery. A system failure releases the reservation.
| Status | Meaning | What to do |
|---|---|---|
| Queued | The task is accepted and waiting for a worker or provider. | Wait. Cancel only if the interface still offers cancellation. |
| Processing | Generation or delivery processing has started. | Do not resubmit. The page may be closed while processing continues. |
| Completed | Delivery QA passed and downloadable artifacts are available. | Preview the loop, then download or import the task. |
| Failed / rejected | Generation, decoding, boundary QA, or another major delivery check did not pass. | Read the final message. System-failed reservations are released; use the task ID when contacting support. |
Know which delivered file to use.
A completed package can contain several representations of the same token. Choose by platform and scene performance, not by the largest number alone.
| File | Purpose | Recommended use |
|---|---|---|
| 512p WebM | Compact transparent animated token. | Default for live play, NPCs, and scenes with many tokens. |
| PNG fallback | Static transparent image. | Portrait fallback, quick inspection, and tools that do not play WebM. |
| Foundry ZIP | Assets, module metadata, README, and import notes. | Manual Foundry delivery or archival handoff. |
| HD / 4K outputs | Higher-resolution review or archive variants when selected. | Important characters, close review, or creator delivery; test performance before live play. |
Finish in Foundry or Roll20.
Foundry with Bridge
Install and enable Bridge as GM, connect the correct Folosa account, then create a task or import a completed one. Bridge verifies files and creates the Actor. Use the complete Bridge guide for installation, security, history, and troubleshooting.
Foundry manually
Download the ZIP, review README and import notes, place files under Foundry Data, and assign the WebM as the Actor prototype token texture. Use the Foundry import guide for the exact package structure.
Roll20
Upload the Roll20-friendly WebM, place it on the tabletop, set its grid size, and test playback in the intended browser. Use 512p first when the scene is busy.
Troubleshooting without duplicate charges.
Most avoidable problems come from changing modes accidentally, weak source composition, or resubmitting before the first task reaches a final state.
The upload looks cropped
Check whether the original already cuts off a limb, weapon, wing, tail, or effect. Upload a source with more surrounding room.
The character changed too much
Use a clearer single-subject image and a motion request limited to visible parts. Remove instructions that add new objects or redesign the costume.
The task seems stuck
Refresh history and read the exact status. Do not submit again while the first task is Queued or Processing.
Foundry did not import
Confirm the connected email, GM role, Bridge version, task completion, and Foundry Data write permission. Then use the Bridge guide.
The token is heavy in play
Use the 512p WebM, reduce simultaneous animated tokens, and test on a representative player device.
A genuine defect remains
Keep the task ID, time, mode, quality, source screenshot, and a short description. Open a support ticket without including passwords or Bridge credentials.
Pre-session acceptance checklist.
- The intended Folosa account owns the completed task.
- The preview preserves the character and keeps important content inside the frame.
- Transparency and the loop look correct.
- The selected WebM plays smoothly in a small test scene.
- The ZIP or Actor is stored where it can be reused without another generation.