Projects & Albums

A project owns a generation workflow, output settings, draft and execution records, and a durable result collection. Project data is user-scoped and stored in PostgreSQL; media is stored under the user's project prefix in the configured object store.

Project Types

Choose the type according to the output you want:

Project type	Output	Common settings
Text	Generated text	System prompt, temperature, maximum tokens
Image	Generated images	Aspect ratio, quality, format, background
Video	Generated video	Duration, resolution, sound, format
Audio	Speech or music, depending on model	Voice/speaker or music mode, output format
ComfyUI Workflow	Images or video from your own ComfyUI	ComfyUI address, API-format workflow, input mappings, output format
Civitai	Images from Civitai checkpoints and LoRAs, or videos from Civitai's Wan and Hunyuan engines	Civitai account, checkpoint, LoRAs and embeddings, negative prompt, size, sampler, steps, CFG, seed

Available controls come from the selected model profile. A project also stores a default provider/model, description, filename prefix, shuffle setting, and workflow.

ComfyUI Projects

A ComfyUI project runs a workflow on a ComfyUI instance you host — a local machine, a LAN box, or a rented GPU. It needs no provider: the instance address lives on the project, because rented instances get a new address every time they start. When the address changes, paste the new one into the project; jobs that are still waiting use it.

1. Address — enter the instance URL (for example http://127.0.0.1:8188) and press Test. Remix Studio connects from its server, so the address must be reachable from where the server runs, not only from your browser.
   • Access password (optional) — only for an instance protected by ComfyUI-Login. Enter the password you log in with, or the API token it prints at startup (For direct API calls, use token=$2b$…, also the first line of ComfyUI/login/PASSWORD). With the password, Remix Studio logs in the way the browser does and logs in again when the session expires; the token is sent as a Bearer header. Leave it empty and no credentials are sent. The password is stored as typed and masked in the form; it is copied when a project is duplicated but left out of project bundles. Set the password in the browser first — Remix Studio won't create one on an instance that has none yet.
2. Workflow — in ComfyUI choose Workflow → Export (API) and upload or paste the exported JSON. A regular saved workflow (with nodes and links) is refused with a hint, because only the API format carries the values that are sent.
3. Inputs — every widget value in the workflow is listed by node.
   • Numbers and toggles are edited in place, starting from the workflow's value. Change one to override it; the reset button (or typing the workflow's value back) drops the override.
   • Seeds are random for every job by default, so a batch does not repeat the same image. Turn off the dice to pin a seed and type it.
   • Text inputs, such as a prompt, choose where their value comes from:
     • Default keeps the value from the workflow.
     • Input takes text you type.
     • Remix builds the value the way a regular project's workflow builds a prompt. It opens a list of workflow items — the same cards a regular project uses — starting from the input's current text. Add text and Add library add items; drag a card to reorder it, and disable, edit or delete it as in a regular workflow. The items are joined in order, separated by a blank line, and every library multiplies the variations: a photo of + a library of 3 subjects + a library of 4 styles gives the prompt 12. The regular workflow's rules apply: deleting an item asks first, an empty text item stops Add to Draft until it is filled or deleted, and a remix with every item disabled stops it too rather than fall back to the workflow's prompt. Deleting the last item leaves the remix open and empty; until an item is added, the input keeps the workflow's value. Leaving a remix of several items asks first, since its items are removed.
   • File inputs, for Load Image, video and audio loader nodes, choose:
     • Default keeps the file named in the workflow.
     • Import takes a file you upload. It is uploaded to ComfyUI's input folder when the job runs.
     • Library varies the input over a media library's items, with the same tag filters a regular workflow uses.

Mapped inputs combine like regular workflow steps: two libraries of 3 and 4 items make 12 combinations, whether they are remixed into one input or feed two different inputs, or a random pick per job with Shuffle. With nothing mapped, the workflow simply runs once per job.

Up to two jobs per project are queued or running in ComfyUI at a time — one generating, the next waiting — and a job stops counting once ComfyUI has finished it, so the next one starts while its result downloads and a slow link to the instance does not leave the GPU idle. A reference file ComfyUI already holds is not uploaded again. Each result is downloaded from ComfyUI and stored like any other generation; a download is only abandoned when no data arrives for a minute, and a job whose result cannot be fetched after three tries fails with the reason — retrying it downloads the finished result rather than generating it again. Choose Image (PNG, JPEG, WebP) or Video output — video files that are not mp4 are converted. A job's expanded view lists the values it sent, including the seed it rolled. When a prompt fails in ComfyUI, the job fails with ComfyUI's own error (for example the node that ran out of memory); when the instance restarted and forgot the prompt, retry the job after updating the address.

Civitai Projects

A Civitai project generates images on Civitai with any checkpoint, LoRA or embedding from its catalog that Civitai can run, or videos with Civitai's video engines (see Civitai video below). Generations are billed to your Civitai account in Buzz. Everything that varies — the checkpoint, the LoRAs, the prompt, the negative prompt and the source image — is a workflow item, so it combines and shuffles like any other workflow step.

Images or videos. Choose Images or Videos when you create the project. You can change it in the project's settings until the project has jobs or results; after that it is fixed, so the album holds only one kind. To make the other kind, create another Civitai project.

Account. Add your Civitai API key as a provider of type Civitai (create the key on Civitai under Account settings → API Keys). The project's settings panel links there when you have none, and picks the account for you when you have only one. The provider's Parallel Tasks setting caps how many generations run on Civitai at once.

Workflow items.

• Checkpoint — one per project. Add a checkpoint by pasting a Civitai model link (https://civitai.com/models/4201?modelVersionId=130072) or AIR (urn:air:sd1:checkpoint:civitai:4201@130072, shown on the model page), or type a name and pick from Civitai's search results. A link without modelVersionId takes the model's newest version. Add several checkpoints to the same item and each job uses one of them, the way a library contributes one item per job.
• LoRA — any number. Each holds one or more LoRAs, LyCORIS, DoRAs or embeddings, again one per job; every enabled LoRA item applies. A LoRA's strength runs −1 to 2 on the slider and −5 to 5 typed; Also try another strength adds the same LoRA at another strength as a further option. Trigger words are listed under each resource — click one to copy it into your prompt.
• Text and text libraries — feed the prompt, or, after clicking their Prompt badge to switch it to Negative, the negative prompt. Several items join in workflow order, as in an image project.
• Image and image libraries — the source image for image-to-image. The first image is used.

Options multiply like libraries do: a checkpoint item with 2 checkpoints, a LoRA item with one LoRA at 0.5 and 1.0, and a library of 3 subjects make 12 combinations. Shuffle picks a random combination for each job instead.

Settings. The panel below the workflow holds what every job shares: size (presets follow the checkpoint — 512–768 px for SD 1.x and 2.x, about a megapixel for SDXL, Pony, Illustrious, Flux and newer; sides snap to multiples of 8), sampler, steps, CFG scale, clip skip, the seed (random for every job by default, or Fixed), the image-to-image Denoise strength, the output format, and Allow mature content, off by default, in which case Civitai blocks mature results and the job fails with its reason.

Image to image. With a source image, the result keeps the image's shape at the area the size asks for — a 1200×600 photo with a 512×768 size renders at 888×440 — and the job records that size. The image is uploaded to Civitai's own storage before the generation is submitted, so it works even when your storage is not reachable from the internet.

Jobs. Every drafted job keeps a copy of the checkpoint and LoRAs its combination picked, its negative prompt and the sampling settings, so later changes leave drafted jobs alone, and it records the seed it ran with; its expanded view lists all of it. Reuse configuration puts a job's workflow and settings back on the project, without its seed. Each job submits one text-to-image workflow to Civitai and is checked every 5 seconds until its image is ready; the image is then downloaded and stored like any other result. A failed generation fails the job with Civitai's reason, and retrying a job whose image was generated but could not be stored downloads it again instead of paying for a new one. Deleting a project cancels its running Civitai generations (Civitai refunds work that has not started).

Album. Each result keeps a record of what it was made with — checkpoint or video engine, LoRAs and strengths, negative prompt, seed and settings — so it outlives the job. Click a result's prompt in the album to see it. Reuse workflow on a result whose job has been deleted still brings back its checkpoint, LoRAs and negative prompt as workflow items. Civitai results can be attached to posts and copied to libraries like any image or video project's.

Civitai video

A video project uses one of the engines Civitai's own generator offers. The engine brings its own model, so a video project has no checkpoint item.

Engine	Resolutions	Length	LoRAs	Negative prompt	From images
Wan 2.2 (default)	480p, 720p	3 or 5 s	up to 2	yes	start frame
Wan 2.1	480p, 720p	3 or 5 s	up to 9	no	start frame
Wan 2.2 5B	580p, 720p	set by the engine	up to 2	yes	start frame
Wan 2.5	480p, 720p, 1080p	5 or 10 s	no	yes	start frame
Wan 2.7	720p, 1080p	2–15 s	no	yes	start and end frame
Wan 3.0	480p, 720p, 1080p	2–30 s	no	yes	start and end frame
Hunyuan	480p	3 or 5 s	up to 9	no	text only

• Settings show only what the chosen engine takes: resolution, aspect ratio, length, and, depending on the engine, CFG, steps, shift, frame interpolation (Wan 2.2 5B), prompt expansion (Wan 2.7 and 3.0) and Prime, Wan 3.0's faster, pricier tier. The seed and Allow mature content work as for images.
• LoRAs must be made for the engine's model (for example Wan Video 2.2 T2V-A14B or I2V-A14B for Wan 2.2). Searching from a LoRA item only finds those, and a LoRA made for another model shows a warning. Past the engine's limit, the first LoRAs are used; engines without LoRAs leave LoRA items out.
• Images start the video: the first image is its first frame and, with Wan 2.7 and 3.0, a second image is its last. The video takes the engine's aspect ratio closest to the start frame. Hunyuan only makes videos from text.
• Results are stored as mp4 files with a poster frame and play in the album like any video project's. Wan 2.2 renders at 12 fps and Civitai doubles that to 24 fps with frame interpolation, as its own generator does.

Project Management

The Projects screen supports search, pagination, and active/archived/all filters. You can:

• Create, edit, and permanently delete projects. Creating and editing open a dialog over the page you are on — full screen on a phone — so you stay on the list or in the project.
• Archive a project to remove it from the default active view, then restore it later.
• Duplicate a project by starting a new project with an existing workflow as the source.
• Rename project folders from the project list.

Archiving is organizational; it does not delete jobs, media, exports, or storage. Deleting a project removes its workflow records, jobs, album records, project objects, and associated export tasks/files. Move individual album items to the recycle bin when you need a recoverable deletion.

Project Workspace Tabs

Draft

Drafts are resolved workflow combinations that have not started. Each stores its prompt, media contexts, provider/model choice, output options, filename, and workflow snapshot. Start one, a selection, or every draft.

Queue

Pending, processing, and failed jobs appear in Queue. You can inspect resolved prompts and contexts, retry failures, delete records, or operate on a selection. See Queue & Concurrency.

Done

Done holds completed job records. It is useful for inspecting or reusing the exact configuration that produced a result. Removing a completed job record is separate from deleting the corresponding durable album item.

Album, Texts, or Audios

The final tab is named for the project modality. It contains durable AlbumItem records created by generation or direct upload:

• Image and video projects provide visual browsing and a lightbox/player.
• Text projects show generated text and its prompt/context; multiple text results can be compared.
• Audio projects provide audio result controls.

The collection supports selection, page-size choices, filename changes, tagging, export, copying and moving to a library or another project, workflow reuse, and recycle-bin deletion. With items selected, these live in one Actions menu. The search box matches an item's name and its prompt across the whole album, not just the page on screen.

The active tab, page, and supported filters live in URL search parameters, so navigation and shared links can preserve the same view. The album opens at 500 items per page; a page size you pick (25 to 500, or all) is remembered for that project in this browser, and an albumSize parameter in a shared link still takes precedence.

Each card or row has a Copy ID for AI button. It copies project:<projectId>/album-item:<itemId>, a reference the assistant or an MCP client can act on directly — paste it into a chat to say exactly which result you mean.

Album files are renamed one at a time from the album; an MCP client can rename many at once with rename_album_items, replacing, adding or stripping a filename prefix, and the job record and file variants are kept in sync either way. Filenames cannot contain %, ? or #.

Tagging Album Items

Every album item carries a free-form list of tags, the same shape libraries use on their items. Tags are how a finished album is organised after the fact — by campaign, round, subject, or whatever the work needs — without moving anything between projects.

Tag a single item with the tag control beside its filename (media cards) or in its row (text and audio lists). To tag many at once, use Tag Selected / Tag All in the toolbar; that dialog offers three operations:

• Add — the given tags are added, existing tags are kept.
• Remove — only the given tags are taken away.
• Replace — the items end up with exactly the given tags; an empty list clears them.

With nothing selected, a batch applies to every item the current filters select, not just the page on screen — so filtering to one tag and adding another retags that whole slice in one action.

The toolbar's tag filter lists every tag in the album with how many items carry it. Selecting more than one tag can mean either Match All (an item must carry every selected tag, the default) or Match Any (at least one), switchable in the same dropdown. The selection lives in the albumTags and albumTagMatch search parameters, so a filtered view can be linked or bookmarked. Clicking a tag chip on an item filters to that tag.

Tags follow the item: they survive a move to the recycle bin and a restore, they are written into project bundles and read back on import, and they are copied onto the resulting library items when album items are copied to a library.

Tags are normalised on write — trimmed, de-duplicated case-insensitively, capped at 64 characters each and 30 per item — so a stray space or a difference in capitalisation cannot split one tag into two entries in the filter list.

Tags From Library Items

A result starts with the tags of the library items it was drafted from. If a draft picked a subject tagged portrait and a style tagged film, the result arrives in the album with both, so the album can be filtered by the same tags as its sources without tagging anything by hand. This applies to drafts made in the app and over MCP, in every project type.

Auto-Tagging

A vision model can write tags for you. Choose it once under Account → Preferences → Auto-tagging: a provider whose models can read images (Google AI, Vertex AI, OpenAI, Claude, Grok or MiniMax), one of its models — custom aliases included — and a concurrency limit, the most tagging requests sent to the provider at once (1–16, default 2). Lower the limit if the provider starts rejecting requests for exceeding its rate limit. Choosing no provider turns auto-tagging off.

Then start a run from an album's Actions menu — Auto-tag Selected, Auto-tag All, or Auto-tag matching items while a filter or search is active — or from the wand button in an image or text library, which covers the selection, the matching items or the whole library. The dialog names the model and skips items that already have tags unless you clear Skip items that already have tags.

• Each item gets 5–10 tags in your interface language. The model is shown the collection's most-used tags and reuses them where they fit, so a library does not end up with portrait, Portrait and portraits.
• New tags are added to the ones the item already has, including any you added while the model was working.
• Images and text are tagged; video and audio are not yet. An image is sent as a small PNG made from its thumbnail.
• A progress bar shows the run, with Stop. Failures stay listed with their reasons until you retry or dismiss them, and a request that hangs for two minutes counts as failed.
• Runs are held in memory, so a server restart drops a run in progress. Start it again with Skip items that already have tags on to pick up where it stopped.

Copying and Moving Results

Copy to… and Move to… in the album's Actions menu open the same dialog. Switch between Copy and Move at the top, then pick where the items go:

• Library — a library of the album's media type: an existing one from the searchable list, or a new one named on the spot. For images and videos, choose Optimized (smaller derived asset when available) or Raw (original generated/uploaded asset).
• Project — another project of the same type: an existing one, searchable by name with its album count beside it, or a new one, which inherits this project's type and generation settings since the results were produced under them.

The dialog previews the items and says what the chosen combination does to the album:

	Library	Project
Copy	Library items are created from the results, with their own copy of each file and their tags. The album is unchanged.	The results are copied with the completed job behind each one and its workflow snapshot, so the Done history and Reuse workflow work in the destination. The album is unchanged.
Move	The results are copied into the library, then go to the recycle bin, where they can be restored until it is emptied.	The results leave this project with their files, the job record behind each one and its workflow snapshot.

With nothing selected, Copy all to… (or Copy this page to… while a filter or search is active) copies without a selection; a move always needs one.

When it finishes you stay on the album, and moved items leave the page at once. The confirmation names the destination and links to it; the link opens in a new tab.

A remembered destination is proposed the next time: the kind of destination per action, and the library or project per media type. Only a completed copy or move is recorded, so browsing the list and backing out does not change the next proposal.

Files are copied into the destination's storage folder, and a name already taken there is given a numbered variant so nothing is overwritten. A copy into a project gets its own files and new record ids, so either project can later be cleaned up without affecting the other; a reference to a library file stays a reference. A move into a project deletes a source file only once nothing left in the source project points at it — a reference shared with a workflow step or with a job that stayed behind is left in place, so both sides keep working. A job that is still running does not move; its album item does, and the job stays with the project its worker is writing into. Only completed jobs are copied.

Watermarking a Single Image

The stamp button on an image album card opens Quick Watermark for that one result in a new tab, without queueing an export, so the album stays where you left it. Close closes the tab when you are done. The page starts from your saved watermark settings — text, position, padding, font size, opacity, and color — and previews them over the image as you change them. When the result has an optimized version, choose Raw or Optimized; the preview shows the version that will be rendered.

Create renders the watermarked image on the server and downloads it to your browser as <name>_watermark.jpg. Nothing is written to storage and nothing appears on the Exports page: the file is sent once, and creating it again renders it again. Changes made on the page are not saved, so your saved watermark — which campaign uploads also use — stays as it was.

Image libraries have the same button on each card, and ComfyUI projects offer it for their image results.

Exports

Export selected album items or the full collection as a named ZIP. For supported assets, choose raw or optimized versions. Image projects can open the watermark configuration screen before queueing the archive.

Exports run outside the generation queue in their own persistent worker and appear on the global Exports page. See Exports & Delivery.

To move a whole project rather than its results, use Export Project on the project card's menu. That produces a project bundle — settings, workflow, album, and media in one ZIP — which the Projects page can import back as a new project via the import button in its header. See Project Bundles.

Reusing Configuration

Job rows retain a workflow snapshot and resolved generation settings. The Reuse configuration action restores those settings into the project editor so a prior result or failure can be used as the starting point for new drafts.

The same action is available from the results themselves, so you can pick a setup by looking at the finished piece instead of a job row:

• Album, text, and audio entries each carry a Reuse workflow control that resolves the settings through the job that produced them.
• The image lightbox offers the same control (shortcut R), and closes on confirmation so you land on the restored workflow.

To start from a result in a different project, choose Import Workflow from the workflow panel's menu. It opens the album picker across your projects of the same type — a Civitai project lists only Civitai projects, a regular project only regular ones; click a result to load the workflow and settings behind it, then confirm to replace this project's. The imported items are copies, so later edits in either project do not affect the other. ComfyUI projects do not offer it.

Reuse changes the current editable workflow/settings only after confirmation; it does not alter the old job or album item.

The snapshot lives on the job record. When it is missing — the Done record was deleted, or the job predates workflow snapshots — the workflow is rebuilt from the result's own prompt and media references instead. A rebuilt workflow reproduces that single result rather than the recipe that varied it, and the confirmation says so before replacing anything. Only a result with neither a prompt nor references reports that no workflow is available.

Orphan Files

An orphan is an object under a project's storage prefix that is no longer referenced by a workflow item, job, album item, or protected trash record. Uploads, retries, edits, and interrupted operations can leave such objects behind.

The Project Orphans screen:

1. Lists every object below the user's project prefix.
2. Collects storage keys still referenced by direct media workflow steps, job outputs/contexts, album outputs/contexts, and trash items for that project.
3. Reports stored objects outside that referenced set, with preview and size where possible.

Selected orphans can be deleted in a batch.

DANGER

Orphan cleanup deletes directly from object storage and cannot be undone. It does not use the recycle bin. Trash records are included in the protected reference set, so valid recycle-bin media is not reported as orphaned.

Use orphan cleanup when project usage is unexpectedly high after many uploads, retries, or edits. It is not a routine replacement for deleting visible album items through Trash.

Finish Notifications

Turn on Notifications under Account → Preferences and the browser notifies this device when a project that was running jobs has none left pending or processing — even with Remix Studio closed. The notification says how it went (All 12 jobs finished., 9 of 12 jobs finished, 3 failed.), and tapping it opens the project. A job that failed and then succeeded on retry counts as finished.

Notifications are switched on per device, and the same card sends a test notification. On iPhone and iPad, Safari offers notifications only to a site added to the Home Screen, so install the app first and turn notifications on from there. The server signs notifications with its own key pair, so no third-party account is needed; see Configuration.

Live Updates

An authenticated WebSocket project hub publishes job, album, trash, and project changes. The viewer refreshes the relevant data when events arrive and falls back to periodic refresh while work is processing if a live connection is unavailable.

Changes to the project's own settings and workflow — made in another tab, by the assistant or by an MCP client with update_project — are reloaded into an open project page as well. The page saves its own edits as you make them, so it skips reloading changes it made itself.

The connection validates the user, account status, project ownership, and session version. It does not expose another user's project events.

The projects list, the libraries list and pages, the campaigns list and pages, the post page, Scheduled Posts, Campaign History and the dashboard refresh the same way, over one per-user change feed at /api/live that each browser tab opens once. It carries only which record changed, never its content, so a page refetches through the normal API; every event is published for a single user, so a connection only ever hears about that user's records. Hidden tabs wait until they are shown again, and a page that lost its connection reloads once it reconnects, since it may have missed changes in between.

Related

• Workflows & Combinations — how drafts are composed.
• Recycle Bin — recoverable album deletion.
• TV, WebDAV & DLNA — watch albums on a TV or open them in a file manager.
• Libraries & Prompts — reusable inputs and result copying.