Queue Uploader
Batch prompts and reference images, run AI video jobs in sequence, retry failures, and download finished clips without watching the browser all night.
Settings
Runs inside the Dreamina/Jimeng generation page as a local browser tool.
Use @ image mentions, preview references, and submit the next job automatically.
Marks failed jobs, keeps moving, and exposes retry, rerun, and download actions.
Made for creators who batch AI video shots.
The product is small on purpose. It wraps the repeated browser work around Dreamina/Jimeng so you can prepare a run, start the queue, and come back to completed, failed, or retry-ready jobs.
Prepare prompts like a production list.
Add scenes, tests, and variations into a visible queue instead of keeping them in a scratch doc while you manually submit one at a time.
Keep reference images attached.
Use @ mentions so each job knows which storyboard, character, or visual reference belongs to it.
Let the queue move.
When one generation finishes or fails, the extension marks it and advances to the next task.
Use it like a small operating manual.
The extension is built for a real Dreamina/Jimeng production loop: prepare the browser page once, add prompts and references into the panel, then let the queue submit, retry, and collect jobs in order.
Open Dreamina/Jimeng in Chrome and sign in to the account you normally use for AI video generation.
The queue runs inside your active browser session, so do not close the generation tab while jobs are running.
-
01
Install and pin the extension
Load the unpacked Chrome extension, pin it if you want quick access, then open the Dreamina/Jimeng video generation page.
- Chrome extensions -> Developer mode -> Load unpacked.
- Open or refresh the Dreamina/Jimeng generation tab after installing.
Seedance QueueEnabledDeveloper mode -
02
Set the generation page first
Choose the model, duration, aspect ratio, quality, and any other Dreamina/Jimeng settings before you start the queue.
- Example: Seedance 2.0, 15s, 16:9, 720p.
- The extension submits into the current page setup.
Seedance 2.015s16:9720pGeneration settings ready -
03
Choose the panel language
Switch the extension panel between English and Chinese. The language choice is saved locally for your next browser session.
- Use English for client demos and overseas workflows.
- Language only changes the panel UI, not your prompt text.
Language中文EnglishLanguage switched to English -
04
Upload reference assets
Add storyboards, character references, style frames, or shot layouts to the asset shelf. Each file becomes an @ mention you can attach to prompts.
- Use clear filenames so @ mentions are easy to read.
- Remove or clear assets without losing the queue.
Assets@storyboard@character@wide-shot -
05
Insert @ references accurately
Type @ to open the asset picker, keep typing to filter, then press Enter, Tab, or click an image. You can also click an asset chip to insert it at the cursor.
- Use @image1, @filename, or @{filename with spaces}.
- The log shows which @ token mapped to which image file.
Follow @storyboard@storyboard-001 -> storyboard-001.png -
06
Write prompts and add tasks
Write each shot prompt with the right @ references, then click Add Current Task to Queue. Build the whole run before pressing start.
- One row equals one generation job.
- Use variations for tests, angles, and camera movement.
Follow @storyboard shot-by-shot. Keep the character consistent with @character.01 cyberpunk alley02 astronaut window -
07
Append more jobs while it runs
You do not have to stop the queue to keep working. While one job is generating, edit the prompt field and add more tasks; new jobs go to the back of the queue.
- Good for building a long overnight run.
- New jobs stay pending until previous jobs finish.
Queue running · 3 pendingGenerating · city shot Pending · forest variation Pending · product closeup -
08
Start, pause, and resume
Start the queue when the list is ready. Pause before changing page settings. If a job has already been submitted, the panel waits for the current job and then stops.
- States include idle, ready, running, paused, and complete.
- The status line also shows whether Dreamina is busy or idle.
Queue runningDone · cyberpunk alley Generating · astronaut window Waiting · calm lake Failed · robot forest -
09
Expand a task before you trust it
Click a queue row to inspect the full prompt, reference count, and image thumbnails. Click a reference image to preview it in a larger overlay.
- Useful for catching the wrong storyboard or character ref.
- Expanded jobs show the real prompt saved in the queue.
2. astronaut looking out window · expandedFull prompt: Use @wide-shot as composition reference...@wide-shot@character-ref -
10
Edit, skip, delete, or retry
Pending, failed, and skipped jobs can be pulled back into the editor. Pending jobs can be skipped. Jobs that are not actively uploading or generating can be deleted.
- Edit restores the prompt and its reference assets.
- Retry moves a failed or skipped job back to pending.
forest robot testFailed · reference restrictionEditRetryDelcalm lake morningPending · 1 imageEditSkipDel -
11
Let failures fail without stopping everything
If Dreamina/Jimeng shows reference restrictions, sensitive content, generation failure, or upload failure text, the current job is marked failed and the queue continues.
- Bad jobs stay visible for later edit or retry.
- The extension does not bypass platform policy or limits.
Current task failed, continuingFailed · reference image restriction Next · already submitted22:10:33 · skipped after failure -
12
Download, rerun, or retry
Download completed clips, rerun useful prompts, or edit and retry failed jobs. The point is to keep the work moving without losing the prompt history.
- Download one clip or all completed jobs.
- Rerun good prompts with the same reference set.
DownloadRerunRetry22:05:11 · downloaded cyberpunk alley intro -
13
Clean up without losing control
Clear refs removes @ image references from the current prompt and tries to remove the real Dreamina reference thumbnails. It does not delete your asset library.
- Clear assets empties the local asset shelf.
- Clear Done removes completed and skipped queue rows.
- Clear All is available after the queue is paused or idle.
Clear refsClear assetsClear DoneClearReference tokens removed; asset library kept. -
14
Tune safety and timing settings
The settings panel lets you require Seedance 2.0 before submitting, adjust idle-stable seconds, and change image upload wait time when the page feels slow.
- Seedance guard helps avoid submitting to the wrong model.
- Idle timing controls when the next job is allowed to start.
SettingsIdle-stable seconds8Image upload wait seconds3.5
Most of the useful v0.1.17 functions, in plain English.
This is the practical feature map for buyers and early testers. It covers the extension workflow, queue controls, reference handling, downloads, safety checks, and what the tool deliberately does not do.
Injected directly into the Jimeng generation page.
Assets, queue rows, and settings are stored in browser IndexedDB.
English and Chinese panel labels.
Upload multiple reference images and keep them as reusable chips.
File names become readable @ tokens, with duplicates handled safely.
Type @, filter assets, choose with mouse, Enter, Tab, or arrow keys.
@image1, @filename, and @{filename with spaces} are supported.
The log shows which @ token matched which local image.
Assets are only attached when the prompt explicitly uses @ references.
Before each submit, old text and old reference thumbnails are cleared.
Add more tasks while a previous task is already generating.
Idle, ready, running, paused, and complete states are shown clearly.
Pending, uploading, generating, done, failed, and skipped rows.
Pause stops the next submission after the current active job settles.
Open a row to inspect full prompt text and attached references.
Click saved references to view a larger preview before reruns.
Move a pending, failed, or skipped job back to the editor.
Skip pending work or delete jobs that are not actively submitted.
Failed or skipped tasks can return to pending without rebuilding them.
Copy a finished task and its references back to the queue tail.
Download a completed job from captured media or the native button.
Trigger downloads for all completed jobs in the queue.
Common reference, content, upload, and generation failures are detected.
Optionally require visible Seedance 2.0 text before submitting.
Adjust idle-stable seconds and image upload wait seconds.
Recent submit, mapping, failure, and download events are shown.
Remove current prompt references while keeping the asset library.
Clear completed rows or clear the whole queue when it is not running.
It does not speed up generation, bypass platform limits, or avoid policy checks.
A separate CLI queue mode exists for users who prefer scriptable batches.
Six practical reasons this is useful.
Batch without babysitting
Queue multiple prompts and let the browser move through them while you work, sleep, or review other shots.
Reference image control
Match each prompt to the right image assets with visible @ references and previewable chips.
Failure-aware flow
Common reference, compliance, or generation failures are marked so one bad shot does not stop the queue.
Download actions built in
Download a completed job, download finished batches, or keep the result visible for later collection.
Rerun from history
Good prompts can be copied back into the queue with their references, making prompt iteration faster.
Local-first workflow
Queue data and asset references are designed to stay in Chrome storage for the extension workflow.
What is included in the first build.
Creators who already run repeated AI video jobs.
AI short video creators
Scene batches, storyboard-to-video tests, camera movement variations, and overnight prompt runs.
Prompt operators
Teams or solo builders who need repeatable submission, retry, and result collection inside the browser.
MVP builders
People who want to see how tiny browser tools can remove one painful workflow without becoming a big platform.
Small product, clear boundaries.
Is this a real product?
Yes. It is an early Chrome extension built around my own Dreamina/Jimeng AI video workflow.
Does it make Dreamina/Jimeng faster?
No. It does not accelerate generation or bypass limits. It automates the repeated submit, wait, retry, and download loop.
Do I need to keep the browser open?
Yes. The extension works inside your browser session, so the generation tab should stay open while the queue is running.
Where is my data stored?
The queue and local asset references are designed for Chrome local storage during the extension workflow.
Can I get early access?
Email me if you already run repeated Dreamina, Jimeng, or CapCut-style AI video jobs and want to test the first version.
Want to test the queue on your own AI video workflow?
Send me what you are batching, how many jobs you run, and where the current workflow gets stuck.