> For the complete documentation index, see [llms.txt](https://docs.memorystring.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.memorystring.app/style-and-motion/transitions.md). # Transitions The 17 single-slide transitions and multi-photo group kinds in MemoryString, and how Auto and How many choose them. Transitions control how each photo enters and leaves. In **Studio**, open Inspector → **Motion** → **Transitions**. The checked boxes are the kinds this show uses. They match the timeline, including groups you pinned. A new show starts with a short list that grows with the number of photos. A show you already saved keeps the list it had. ![Motion → Transitions: How many, Auto, and the kinds this show uses](https://316881897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6lG8Zi4VdmddHJ8jUOT5%2Fuploads%2Fgit-blob-45eb5e68f0fd4bdae7d959ec74cfd18bdd33e8a1%2Finspector-motion-transitions.png?alt=media) ## How many **Single slides** and **Multi-photo groups** each have a **How many** slider and an **Auto** switch. **Auto** follows how many photos are in the show: | Photos | Single-slide transitions | Group kinds | | -------------- | ------------------------ | ----------- | | Up to about 12 | 2 | 1 | | About 13 to 30 | 3 | 2 | | About 31 to 60 | 4 | 3 | | Longer | 5 | 3 | Drag **How many** and **Auto** turns off. The line under the slider reads **Auto · 2** or **Custom · 3**, and the show re-cuts to that many kinds. Check or uncheck a kind and the show re-cuts the same way. The line says **Custom**. **Shuffle** keeps the kinds you checked by hand and redraws the rest, then cuts the show again. Set group **How many** to **0** for a show with no multi-photo groups. Each of these is one undo (**⌘Z**). At least one single-slide transition stays on. Option-click a single-slide row to use only that one. **Reset Motion to Defaults** puts both **How many** controls back on **Auto** and restores this Look's motion settings. Slide order and durations stay. Clicking a **Look** deals a fresh short list for that Look. A group kind you turned off, such as **Perspective Pair**, stays off. Check it again to bring it back. See [Looks](/style-and-motion/looks.md#the-eight-chips). Energy does not turn a checked kind off. ## Single slides One photo at a time. At least **one** transition type stays on. MemoryString has **17** single-slide types. A show uses the ones that are checked. ### Ken Burns Slow zoom toward the focus point. {% embed url="" %} ### Depth dissolve Photo sharpens from blur. {% embed url="" %} ### Layers Outgoing photo fades while the next appears. {% embed url="" %} ### Card flip Card flips in and out. {% embed url="" %} ### Slide rotate Card slides in from off-screen and slides out. {% embed url="" %} ### Spark slide Card slides with a spark trail. {% embed url="" %} ### Sparkle wipe Glitter trail as the next photo arrives. {% embed url="" %} ### Flying card Card moves through 3D space. {% embed url="" %} ### Offset wash Photo on one side, color wash on the other. {% embed url="" %} ### Punch-in Fast zoom through the frame. {% embed url="" %} ### Spiral-in The card winds in on one spiral, about two turns, and keeps crawling through the hold. The exit continues the same way. A wash zooms behind it. {% embed url="" %} ### Reveal from depth Photo pushes forward out of blur. {% embed url="" %} ### Accordion fold Fold animation in and out. {% embed url="" %} ### Contact sheet One sharp photo on a dim grid of the same image. {% embed url="" %} ### Same-photo fan One photo with soft side copies. {% embed url="" %} ### Motion trail Photo moves with a motion echo. {% embed url="" %} ### Swirl-in The card comes in from far away while it turns about one and a half times, then sits face-front. The exit turns back out. {% embed url="" %} **Spiral-in** and **Reveal from depth** wind in slowly, so their slides run a little longer than the rest. They play at every **Energy**. Captions wait until the photo nearly lands. Per-slide pick: right-click → **Slide Transition** (includes **Random**). See [Library](/build-your-movie/library.md#right-click-a-slide). ## Multi-photo Several photos in one beat: **3D Ribbon, Carousel, Filmstrip, Perspective Pair, Photo Stack, Scatter & Settle**. Checked kinds are the ones this show groups with. You can check every kind. A short show does not turn a box back off. **Auto** picks a short list from the length of the show, up to three kinds (see the table above). **How many** at **0** leaves one photo at a time. **Perspective Pair** is not forced. **Auto** may still pick it as one of the kinds. Uncheck it and those pairs become single slides. When there is room, another slide sits between the two shots. It stays off after **Shuffle**, a length change, reopening the project, and clicking the **Look** again. Check it to bring the pairs back. **⌘Z** restores them. Details: [Multi-photo groups](/style-and-motion/groups.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.memorystring.app/style-and-motion/transitions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.