# How to Create and Modify PowerPoint Animations and Transitions Using OfficeCLI > Master PowerPoint animations and transitions via command line with OfficeCLI. Learn to add, set, and remove effects programmatically for efficient presentation control. - Repository: [OfficeAI/OfficeCLI](https://github.com/iofficeai/OfficeCLI) - Tags: how-to-guide - Published: 2026-08-07 --- **OfficeCLI enables command-line manipulation of PowerPoint presentations through semantic paths like `/slide[n]/shape[m]/animation[k]`, supporting `add`, `set`, and `remove` operations to control animation triggers, duration, and motion paths without opening the GUI.** OfficeCLI from the iOfficeAI/OfficeCLI repository exposes PowerPoint's animation layer as a hierarchical object model that you manipulate via discrete terminal commands. By targeting specific shapes and charts through semantic addressing, you can programmatically inject new effects, modify existing timing parameters, or delete animation entries entirely while the library handles underlying Open XML serialization. ## Semantic Path Syntax for Animations OfficeCLI identifies animation targets using a slash-delimited path structure that mirrors the document's object hierarchy. The parser recognizes the pattern: ```bash /slide[]/(shape|chart)[]/animation[] ``` - **``** — The 1-based slide index - **``** — The 1-based shape or chart index on that slide - **``** — The 1-based animation index attached to that object According to the source code in [`PowerPointHandler.cs`](https://github.com/iOfficeAI/OfficeCLI/blob/main/PowerPointHandler.cs) (lines 694-698), the `Query` method validates these paths using the regular expression: ```csharp ^/slide\[(\d+)\]/(shape|chart)\[(\d+)\]/animation\[(\d+)\]$ ``` This regex extraction allows the CLI to locate the specific Open XML nodes representing the animation effect. ## Core Animation Operations The CLI provides three primary commands for animation manipulation. Each operates on the semantic path defined above. ### Add Animation The `add` command inserts a new animation entry at the specified index on the target shape. When executed, `PptxBatchEmitter` (lines 2133-2137) serializes the operation into a batch item that guarantees round-trip fidelity. ```bash officecli add /slide[2]/shape[1]/animation[1] "animation=fade;trigger=onclick;duration=2" ``` ### Set Animation The `set` command updates properties of an existing animation without affecting unspecified fields. The implementation in [`PowerPointHandler.Set.cs`](https://github.com/iOfficeAI/OfficeCLI/blob/main/PowerPointHandler.Set.cs) (lines 283-306) extracts properties such as `trigger`, `duration`, and `motionPath` from the command string and applies them to the underlying Open XML elements. ```bash officecli set /slide[2]/shape[1]/animation[1] "duration=3;trigger=after" ``` ### Remove Animation The `remove` command deletes the animation entry entirely from the shape's animation list. ```bash officecli remove /slide[5]/shape[4]/animation[2] ``` ## Animation Properties Reference When using `add` or `set`, you supply properties as semicolon-delimited key-value pairs. The following fields are recognized by the CLI: | Property | Acceptable Values | Description | |----------|-------------------|-------------| | `animation` / `animate` | Valid Open XML types (e.g., `fade`, `fly`, `wipe`, `zoom`, `motionPath`) | Specifies the visual effect type. | | `trigger` | `onclick`, `click`, `after`, `afterprevious`, `with`, `withprevious` | Defines the start condition relative to user interaction or other effects. | | `duration` | Numeric (seconds, e.g., `2.5`) | Length of the animation in seconds. | | `delay` | Numeric (seconds) | Pause before the effect begins. | | `motionpath` / `motionPath` | SVG-like path commands (e.g., `M0,0 L3000000,0`) | Custom motion trajectory for path-based animations. | | `zorder` / `z-order` | Integer | Stacking order relative to other effects on the same shape. | Omitted properties retain their existing values during `set` operations, while `add` operations apply PowerPoint defaults for unspecified fields. ## Implementation Details from Source Code ### Path Parsing and Node Resolution The `PowerPointHandler.Query` method (lines 694-698 of **PowerPointHandler.cs**) acts as the entry point for resolving semantic paths. It maps the regex-captured indices to actual slide parts and shape objects within the Open XML package. ### Shape-ID Bookkeeping After any raw XML modification, the handler invokes `InitShapeIdCounter` (lines 662-667) to rebuild the internal shape-ID table. This ensures that newly added animations receive fresh, non-conflicting `cNvPr` IDs, preventing identifier collisions during subsequent operations. ### Batch Emission for Fidelity When you save a presentation, `PptxBatchEmitter` processes animation changes by emitting one `add animation` batch item per effect (lines 2133-2137). This architecture preserves complex scenarios such as multi-effect shapes and custom motion paths through dump-batch-replay cycles. ## Practical Command-Line Examples Replace `` with your target presentation path in the following snippets. Add a fade-in animation triggered by click: ```bash officecli add /slide[2]/shape[1]/animation[1] \ "animation=fade;trigger=onclick;duration=2" ``` Apply a custom motion path moving 3 cm to the right over 1.5 seconds: ```bash officecli add /slide[3]/shape[2]/animation[1] \ "animation=motionPath;motionPath=M0,0 L3000000,0;duration=1.5;trigger=after" ``` Update an existing animation's trigger from automatic to manual: ```bash officecli set /slide[3]/shape[2]/animation[1] "trigger=onclick" ``` Adjust duration independently: ```bash officecli set /slide[2]/shape[1]/animation[1] "duration=3" ``` Delete a specific animation effect: ```bash officecli remove /slide[5]/shape[4]/animation[2] ``` ## Summary - **Semantic paths** (`/slide[n]/shape[m]/animation[k]`) provide precise addressing for PowerPoint animations via command line. - Three operations control the lifecycle: **`add`** creates entries, **`set`** modifies properties selectively, and **`remove`** deletes effects. - Supported properties include **trigger**, **duration**, **delay**, **motionPath**, and **zorder**, accepting standard Open XML values. - The `PowerPointHandler.Query` method validates paths using regex matching against shape and animation indices. - Internal **shape-ID bookkeeping** via `InitShapeIdCounter` prevents ID conflicts during batch operations. - **`PptxBatchEmitter`** guarantees round-trip serialization fidelity by emitting discrete batch items for each animation change. ## Frequently Asked Questions ### Can I animate charts using the same syntax as shapes? Yes. According to the regex implementation in [`PowerPointHandler.cs`](https://github.com/iOfficeAI/OfficeCLI/blob/main/PowerPointHandler.cs) (lines 694-698), the path accepts either `shape` or `chart` as the object type. Use `/slide[n]/chart[m]/animation[k]` to target chart objects specifically. ### What happens to unspecified properties when using the set command? OfficeCLI preserves existing values for any properties you omit. Only the explicit key-value pairs you provide in the command string are applied to the underlying Open XML, leaving other animation attributes untouched. ### How does OfficeCLI prevent ID conflicts when adding multiple animations? After every raw XML change, the library rebuilds its internal shape-ID table through the `InitShapeIdCounter` method (lines 662-667). This ensures each new animation receives a unique `cNvPr` identifier that does not collide with existing elements. ### Are slide transitions supported alongside shape animations? While the provided source analysis focuses on shape-level animations via `/slide/shape/animation` paths, the semantic path architecture suggests similar patterns could apply to slide transitions. However, the specific implementation details for transition manipulation are not covered in the analyzed `PowerPointHandler` and `PptxBatchEmitter` source files.