Name the automation so we can stop lying about it
What “smart” actually is in this codebase
Photos use object-fit: cover, so they fill the pane without stretching. You drag to set object-position (focusX/focusY). Slide count is a number you type with plus/minus. html2canvas slices the strip. JSZip packs files. Default collage maps (in the other mode) are a lookup by image count — authored CSS, not a network that “understands” a birthday. None of that is a large language model or a diffusion model. Calling it AI in the URL matches how people search. The body of this page exists to retire the hallucination that we generate Instagram carousels from a sentence.
A honest workflow if you do use generative tools
Generate stills wherever you are allowed to. Download them. Convert weird formats. Drop them here as if they were camera files. Pan so faces the model almost got sit in the safe center. Export ZIP. You still own the rights conversation for generated media; we will not launder that. Bulk “ten product carousels from a CSV” is not a feature — repeat the drop for each SKU or use a real PIM. Auto layout suggestions beyond cover-fit do not exist; if a competitor shows a magic arrange button, ask whether it uploaded the shoot to do it.
Why local still wins next to AI SaaS
Most prompt-to-carousel products require an account and a copy of your brand photos “to learn the look.” This filmstrip does not need that copy. Pair them: generate public-safe textures in a model, keep customer-confidential photography in this tab, combine only on your disk. That hybrid is the grown-up version of “AI carousel maker,” and it does not require us to pretend Canvas is a foundation model.