Skip to content

Commit 901a5dd

Browse files
authored
Update VAE definition and its implications in workflows
1 parent 641f12c commit 901a5dd

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

docs/tips/terminology.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -100,16 +100,16 @@ When a guide says a model is "DiT-based," it usually means the main denoising en
100100

101101
**VAE**
102102

103-
VAE stands for Variational Autoencoder. In image-generation workflows, the VAE is the component that converts between normal image pixels and the model's compressed latent space.
103+
VAE stands for Variational Autoencoder, or sometimes referred to as Variable Auto Encoder. In image-generation workflows, the VAE is the component that converts between normal image pixels and the model's numerical, sometimes compressed if using a UNet workflow, representative latent space.
104104

105105
You can think of it as a translator between two worlds:
106106

107107
- VAE encode: image -> latent
108108
- VAE decode: latent -> image
109109

110-
The denoiser usually works in latent space because latent tensors are much smaller than full-resolution images, which makes diffusion practical on consumer hardware. The VAE is what lets the pipeline move into that smaller space and back out again.
110+
The denoiser usually works in latent space because latent tensors are much smaller than full-resolution images, which makes diffusion practical on consumer hardware. The VAE is what lets the pipeline move into that latent space and back out again.
111111

112-
This is also why the wrong VAE can visibly damage output. Common symptoms include washed-out colors, odd contrast, muddy textures, or images that simply do not decode correctly. In older SD and SDXL workflows, matching the intended VAE can matter a lot.
112+
This is also why the wrong VAE can visibly damage output. Common symptoms include washed-out colors, odd contrast, muddy textures, or images that simply do not decode correctly and resulting in error. In older SD and SDXL workflows, matching the intended VAE can matter a lot.
113113

114114
**Latent**
115115

0 commit comments

Comments
 (0)