# The Plugin Manifest
Learn how to configure your plugin manifest file.

Every Lottie Creator plugin requires a `manifest.json` file that defines its metadata and entry points. This file tells Lottie Creator how to load and display your plugin.

## Manifest structure

Here's a complete example of a plugin manifest:

```json
{
  "id": "befe6a87-feed-4a16-9a0a-6bd5f206d092",
  "name": "Duplicator Plugin",
  "apiVersion": "1",
  "entry": "plugin.js",
  "ui": "ui.html"
}
```

## Required fields

| Field        | Type   | Description                                               |
| ------------ | ------ | --------------------------------------------------------- |
| `id`         | string | A unique UUID identifying your plugin                     |
| `name`       | string | The display name shown in Lottie Creator's plugin list    |
| `apiVersion` | string | The Creator API version. Currently `"1"`                  |
| `entry`      | string | Path to your compiled plugin code (usually `"plugin.js"`) |
| `ui`         | string | Path to your UI HTML file (usually `"ui.html"`)           |

## Best practices

### Choosing an ID

- Use a valid UUID v4
- Keep the same ID when updating your plugin
- Don't reuse IDs between different plugins

### Naming your plugin

- Keep names short and descriptive (2-4 words)
- Avoid generic names like "My Plugin" or "Tool"