Archive

Keep published history in Livebound and optionally move published files into a structured archive.

Livebound has two related but separate archive actions: archiving the post record and moving the published image files.

Archiving a post takes it off the board. The line beside the button says what that does not do: no file is moved.
Archiving a post takes it off the board. The line beside the button says what that does not do: no file is moved.
Done — and it says so again, because the two halves are easy to confuse.
Done — and it says so again, because the two halves are easy to confuse.
The archive view: the post with its pictures, and no folder beside it yet. Nothing has moved.
The archive view: the post with its pictures, and no folder beside it yet. Nothing has moved.
The archive folder on disk at that moment: empty. Moving the files is a second decision.
The archive folder on disk at that moment: empty. Moving the files is a second decision.
When you take it, every path is listed first — moved, not copied, and nothing overwritten.
When you take it, every path is listed first — moved, not copied, and nothing overwritten.
The word has to be typed before the button will do anything. This is the one action here that cannot be taken back.
The word has to be typed before the button will do anything. This is the one action here that cannot be taken back.
Afterwards the same view names the folder, and the run reports what it moved and what it tidied up.
Afterwards the same view names the folder, and the run reports what it moved and what it tidied up.
On disk: one folder per post, dated and named by its CivitAI id.
On disk: one folder per post, dated and named by its CivitAI id.
And inside it, each image beside the sidecar that belongs to it.
And inside it, each image beside the sidecar that belongs to it.

Archive a post on the Board

Archiving a published post removes it from the active Board workflow and places it in the Archive view.

This action changes Livebound’s post state only. It does not move image files.

The Archive view keeps published history available with date filters and links back to CivitAI.

Move published files into the archive folder

The file move is an explicit action in Settings. Livebound first shows the move plan, then moves files only after you start the operation.

Only images from posts you have already moved to Livebound’s archived post state are eligible, and the file move still requires exact publication identity rather than visual similarity alone.

The normal folder format is:

YYYY-MM-DD__<remote_post_id>

If the publication date is not known, the post ID alone can be used until the folder can later be renamed to the dated form.

Where a remote image ID is known, Livebound can include it in the archived filename. Sidecar files move with their image where supported.

Files are moved, not copied. Name collisions do not overwrite an existing file; Livebound chooses a free name instead.

Archived folders remain part of Livebound’s view of the library. Keeping all files associated with a published post is deliberate even when several local files correspond to the same visual image.

Back up the archive itself

The database backup does not contain the image archive. Settings can create a ZIP of the archive folder separately, either as one file or split into 500 MB, 1 GB, or 4 GB parts.

The archive ZIP uses no additional compression because the image formats are already compressed.