GUI howtos

Image Output Filename Format

Starting from version 0.2.1, a new setting is available under Settings -> Diffusion that lets you customize the filenames of generated images (excluding the file extension).

You can use the following tags to define the filename structure:

Tag	Description
[year]	Current year
[month]	Current month
[day]	Current day
[hours]	Hour of image creation
[minutes]	Minute of image creation
[seconds]	Second of image creation
[finished_at]	Unix timestamp when the job finished
[created_at]	Unix timestamp when the job was created
[updated_at]	Unix timestamp when the job was updated
[jobid]	Internal ID of the job
[seed]	Initial seed used for the generation
[batch]	Number of images generated in a single job
[width]	Image width in pixels
[height]	Image height in pixels
[mode]	Generation mode (e.g., txt2img, img2img, upscale)
[model]	Name of the model used
[model_sha256]	sha256 of the base model. If the model is not hashed, it's an empty string
[steps]	Number of steps used to generate the image
[steps_total]	Total steps used (including tiling steps)
[cfg_scale]	CFG scale value used
[denoising_strength]	Denoising strength applied

Example

If you include a directory separator (/) in the filename, such as:

[mode]-[year]-[month]-[day]/[jobid]_[width]x[height]

a corresponding directory will be created in the output folder, and the images will be saved within it.

Conflict Handling

If a file with the same name already exists, the new image will be saved with a suffix in the format _\<number>.ext to avoid overwriting.

The default format is:

[mode]_[jobid]_[seed]_[width]x[height]

Forcing a Specific Backend

The GUI allows you to force the use of a specific Stable Diffusion C++ backend. These backends are compiled as separate shared libraries, and you can specify which one to load using the following parameters:

Parameter	Backend
-avx	stable-diffusion_avx
-avx2	stable-diffusion_avx2
-avx512	stable-diffusion_avx512
-cuda	stable-diffusion_cuda
-hipblas	stable-diffusion_hipblas
-vulkan	stable-diffusion_vulkan

Note: Vulkan binaries are not currently built.

You can also build a custom backend using Stable Diffusion C++. Ensure that the GUI version matches the corresponding sd.cpp version (based on the Git tag) before launching the GUI with your custom backend.