AMD Creative Factory
Turn a description or an image into a short video with sound, or straight into a still image. All of it on AMD GPUs.
Video and Image are separate
Video and Image in the top bar are two separate pages. Each has its own model list, its own work list and its own Explore feed. Whichever you pick, you only see that kind of output — no videos mixed into the image page.
They are split because they are not the same thing: video has a duration, has sound and comes out as MP4; an image has none of those and comes out as PNG. The URLs are separate too — bookmark or share /video and /image directly.
The site root redirects to Video, so old bookmarks keep working.
What Video does
- Text to video — write a description and get a shot from nothing.
- Image to video — supply an image as the first frame and describe how it moves.
- First & last frame — give a start and an end image; the model fills in between.
Output is MP4 at 24 fps, 768px on the short edge, with a generated stereo soundtrack. Aspect ratios: 16:9, 9:16, 1:1, 4:3, 3:4, 21:9 — portrait and landscape are native, not cropped.
What Image does
- Text to image — write a description, get a PNG.
Output is PNG, with the same choice of aspect ratios; exact pixel sizes depend on the model. Text to image is the only task type here for now — image upload, duration and sound do not appear on the Image page at all. They are not hidden; they genuinely do not exist for images.
Image models run on AMD Radeon™; video runs on AMD Instinct™. It makes no difference to you — same API, same credits, same retention.
Six steps
- Sign in with your AMD account. First sign-in grants 100 credits: about 16 five-second videos, or 100 images.
- Pick Video or Image in the top bar. This decides which models you can pick and whether a duration control exists at all.
- Write a prompt in the bar at the bottom. Up to 8,000 characters.
- Adjust by tapping + for model and aspect ratio — plus duration and input type on the video side. The defaults suit most cases.
- Generate. Five seconds of video takes about 25 seconds; a 1024×1024 image about 50. Queue position and elapsed time update live.
- Publish — optional. Share it to Explore for everyone to see.
Writing prompts
Say how the camera moves. If you don't, the model decides, and the result is often nearly static. A structure that works:
subject + specific action → camera move → light and mood → medium
Example:
A lighthouse on a black volcanic shore, surf rolling in and
dissolving into foam;
the camera drifts slowly sideways from above;
low dawn light rakes across the water from the right, turning
the spray amber;
photorealistic, shallow haze, natural colour grading.For video you can describe sound as well as picture — surf, rain, room tone. For images only the picture half applies. Everything in Explore has a copy-prompt button.
Duration
Frame count lands on a 17n+5 lattice at a fixed 24 fps, so asking for 5 seconds delivers 5.167. The ticks on the duration slider are those positions; nothing exists between them. Between 4 and 15 seconds, 8.000s is the only whole second. Billing follows the delivered length.
This section is about video only. Image models have no duration: the control disappears from the interface, and passing duration to the API changes nothing.
Credits and redemption
New accounts get 100 credits. Each generation holds credits when you submit, charges them on success and refunds them in full on failure. Cancelling after the task has started on a GPU is not refunded.
| Video (MiniMax-H3) | 1 credit per delivered second, rounded up: a 5-second video costs 6, a 15-second one 15 |
|---|---|
| Image (Qwen-Image 2.1) | 1 credit per image at the default 30 steps; more steps cost proportionally more, e.g. 2 credits at 40–50 steps |
| Image (Qwen-Image 2.1 Turbo) | 1 credit per image |
The cost of the current generation is shown next to the Generate button. When your balance is not enough the button is disabled and tells you how much is missing.
Where to see your balance
Your balance is shown in the account menu at the top right and on the Account page. The Account page also lists every grant, hold, charge, refund and redemption, each tied to its task.
Where codes come from
- Event codes: handed out at AMD workshops, hackathons and similar events. They look like CF-XXXX-XXXX-XXXX.
- AMD AI developer program: exchanging developer points for Creative Factory codes is not open yet. This page will say so when it is.
How to redeem
Open Redeem credits on the Account page (the same entry is in the account menu at the top right, and next to the Generate button when you are short), paste the code and submit. Case, spaces and dashes do not matter, and the letters O, I and L are read as 0, 1 and 1. Credits arrive immediately and the balance updates without reloading the page. Each code can be used once per account.
If redemption fails
| Invalid, expired or already used | Check for typos, the expiry date, and whether this account has used it already. If it still fails, contact whoever gave you the code. |
|---|---|
| Too many attempts | Each account may fail at most 10 times an hour. Try again in an hour; successful redemptions do not count. |
| Developer program codes are not available yet | Only event codes can be redeemed for now. |
| Sign in again / Please try again later | Your session expired or the network failed. Sign in again or retry later; a code is not used up unless redemption succeeds. |
Over the API, insufficient credits return HTTP 402 (base_resp.status_code=1002 on v1), and the error carries a link to this section.
Keeping your work
Results are kept for 7 days; each card shows how long is left. Press Keep to hold one indefinitely, up to 20 at a time. Anything published to Explore never expires.
Download links are signed and valid for 24 hours. They need no login, so browsers, ffmpeg and ComfyUI can fetch them directly — and so can anyone else holding the link.
Publishing to Explore
Finished work has a Publish button, for video and images alike. Publishing puts it in a review queue; once an admin approves it, it appears in the Explore feed of its own tab — video in Video, images in Image. Your nickname and prompt become public too — the confirmation says so. You can unpublish at any time, with no review and no delay.
Review exists because the site runs on an AMD domain, so anything public carries that brand.
Limits
| Prompt | 8,000 characters |
|---|---|
| Duration | Video 4–15 seconds, snapped to the lattice; images have none |
| Input image | 30MB, video only |
| Queued at once | 5 tasks |
| Retention | 7 days, up to 20 kept |
| Cancelling | Queued tasks cancel instantly. Tasks already on a GPU finish, are discarded, and the credits refunded |
Using the API
Everything in the interface is available over HTTP, wire-compatible with the MiniMax video generation API. Video and images share one API: you change the model and task fields, not the endpoints. Request and response shapes, status codes and error types are in the API reference; runnable samples are on the home page under the API tab.