# AnimatePresence custom > Pass dynamic data from AnimatePresence into exiting variants. **Source:** [https://motion.svelte.page/docs/animate-presence-custom](https://motion.svelte.page/docs/animate-presence-custom) --- `AnimatePresence` accepts a `custom` prop for data that exiting children still need after they have been removed from Svelte state. This mirrors Motion's presence context: exit variants resolve with the latest parent `custom` value, falling back to the motion element's own `custom` only when the parent doesn't provide one. ```svelte ``` > Live example: [/examples/animate-presence-custom](https://motion.svelte.page/examples/animate-presence-custom) ## Why parent custom matters When a child is removed, its props are already stale. A directional carousel needs the new navigation direction to tell the old slide where to exit. Passing `custom={direction}` to `AnimatePresence` makes that direction available to the exiting variant at the exact moment the exit animation is resolved. ## API Reference ### `` - **`custom`** — any value forwarded to dynamic exit variants. - Exit variants receive the `AnimatePresence` custom value before the element's own `custom` value. - If `AnimatePresence custom` is `undefined`, the element's inherited `custom` value continues to drive variants. ## Related - [`AnimatePresence`](/docs/animate-presence) — coordinate enter and exit animations - [`Variants`](/docs/variants) — named animation states and function-form variants Based on [Motion's AnimatePresence custom API](https://motion.dev/motion/animate-presence/#custom).