Projects

A project is one piece of work: a short film, a commercial, a music video, or any other set of shots you want to plan and generate together. Each project has its own shots, characters, runs, and artifacts. Switching projects is how you keep different productions cleanly separated.

All project management lives on the File menu in the menu bar:

  • New Project. Opens a form to name the project and pick its output root folder.
  • Open Project. Shows the list of all your projects so you can search for one and open it.
  • Open Recent. Lists the five projects you opened most recently, newest first. One click reopens any of them. Archived projects are left out.
  • Close Project. Closes the current project and brings up the Open Project modal again.
  • Project Settings. Opens the settings form for the project that is currently open.
The File menu open, showing all the project actions.

Every time you launch 1stUnit, and every time you close a project, the app shows the Open Project list. It never auto-opens the last project. This is intentional. It gives you a chance to switch contexts before any data loads.

The list is built for many projects:

  • Search. Type part of a project's name or folder to narrow the list.
  • Active and Archived tabs. Your current projects are under Active. Projects you archived are under Archived (see below). Each tab shows how many projects it holds. If your search only matches archived projects, the list offers to show them.
  • Sort. By last opened, name, or date created. The app remembers your choice.
  • Rows. Each project shows its name, its folder, when you last opened it, and how many work items it has.

Click a project and choose Open, or double-click it. You can also use the arrow keys and press Enter. The + New project button creates a new one.

The Open Project list with a search box, Active and Archived tabs, a Sort menu, and six projects showing their folders, last-opened dates, and item counts.

Project Settings are specific to the project that is open. They cover:

  • Project name. Rename the project at any time. The new name shows in the title bar and on the recent list.
  • Output root folder. Where the project's files live. Changing this affects only new work items going forward. Existing work items keep their original folder paths so nothing breaks.
  • Default generation settings. Defaults that pre-fill the New Run form when you start a new run.

You can open Project Settings either from the File menu or from the Settings button in the top bar of the pipeline board.

The Project Settings form with the project name, output root path, default generation settings, and the Archive section.

When a project is finished, you can archive it to keep the Open Project list short. Archiving only hides the project from the Active tab and from File > Open Recent. Nothing is deleted: its work items, takes, and files stay exactly where they are.

To archive the project that is open, go to Project Settings, find the Archive section at the bottom, and click Archive project. 1stUnit asks you to confirm first. The project stays open, and an amber ARCHIVED badge appears next to its name on the pipeline board and in Project Settings.

The Archive section of Project Settings asking to confirm archiving Horizons Reset Trailer, with Cancel and Archive project buttons.

An archived project still opens normally from the Archived tab, and it stays archived while you work in it. To bring it back to the Active tab, open it and click Restore project in the same section of Project Settings. Restoring is only done there.

1stUnit keeps two separate settings areas, and the distinction matters:

  • Preferences (Edit menu) are app-wide. The Runway API key lives here. Whatever project you have open, the same key is used.
  • Project Settings (File menu) are per project. The name, output folder, default generation settings, and archiving only apply to the project that is open.

Each project has its own folder tree inside its output root. Folders are named by type and number, never by your custom labels, so paths stay stable even if you rename a scene or a character later. Here is what a typical project tree looks like:

A file explorer view showing the Scenes and Characters folders under a project root, with subfolders for Scene 001, Shot 001, Characters/Hank/Prototype, and so on.

Everything 1stUnit knows about your projects is also stored in a single database file at %APPDATA%\1st-unit\1stunit.db on your PC. All your projects share this one file. The files inside your output root are the actual generated images and videos. The database tracks what was generated, when, with which prompt and inputs, and what verdict you gave each take.

When an update changes how the database is organized, 1stUnit first saves a copy of it next to the original, for example 1stunit.db.before-schema-1.bak. This happens once, the first time you open the updated app. You can delete the copy once you are happy that everything works.

1stUnit remembers the size and position of its window between launches. If you maximize it, it stays maximized next time. If you move it to a second monitor, it reopens there. The one exception is when the saved position lands entirely off the visible desktop, for example after a monitor is unplugged. In that case, the app will fall back to a sensible default size so the window will not get stranded.