> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-admin/embed-and-extend-pentaho-functionality-cp/embed-and-extend-pdi-functionality/extend-pentaho-data-integration/create-pdi-icons.md).
# Create PDI icons
This design guideline is intended to help you maintain consistency with other user interface elements within Pentaho Data Integration. It's recommended that you create your icon in vector shapes using a design tool which saves or exports to Scalable Vector Graphics (SVG) Version 1.1 format. Vector shapes allow assets to be scaled up without loss of detail and crisp edges.
{% hint style="info" %}
**Note:** The W3C offers a [list of programs](http://www.w3.org/Graphics/SVG/WG/wiki/Implementations) that support SVG.
{% endhint %}
## The anatomy of a PDI icon
This section reviews the breakdown of what goes inside the icons.
| Icon | ID | Description |
| ----------------------------- | ---------------------------------- | ----------------------------------- |
| Kaq2qL1d8y4x | 1: Icon fill color | The primary stroke color is #3D6380 |
| 2: Icon border color | The primary stroke is 1.7pt | |
| 3: Icon foreground line color | The secondary stroke size is 0.8pt | |
## Positioning action indicators
| Icon | ID | Description |
| ------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| WOnohT1pjgLK | 1: Action indicator | For any PDI icon which requires an action indicator, the icon must have the secondary element placed in the top-left or bottom-right corner of the icon. |
| 2: Forty-five degree slice for positioning action indicators | The primary element within the icon is recommended to have a 45ยบ angle sliced through, and the secondary element placed in that spot. | |
### Action indicator badges
| Icon | Description | Icon | Description | Icon | Description |
| ------------ | ----------------------------------------------- | ------------ | ----------------------------------------------------------- | ------------ | ------------------------ |
| RHI5mmNZpAzj | Input / Import /Get / Download / Extract / Read | KTEYcPxY2hcV | Output / Upload /Export / Insert /
Put / Write
| 13xuOgxMi4mh | Validate |
| hmSlB5RIQ2nK | Create | pW6NXSq5aehC | Compare | TC305whPrOn0 | Wait |
| lH8WMFIg1QWx | Block | lsvj15rA3FFG | Execute / Call | EGSzcoakgDNe | Search / Lookup / Exists |
| mIwBr811CXmv | Bulk Load | SiB2oxBXmr3r | Encrypt | qJSswQBpuq9Y | Generator /Processor |
| SJSBsi8QWyeR | Delete | cCHC0ws0fBJx | Decrypt | pwSfS6lMcXrm | Upsert |
| YRQ0hE0oTpgQ | Update | Xy4kFnqiAXSA | Move | AZCZpallXDEJ | Set |
## Color palette
## Downloading PDI icon template
You can use the SVG template file, `PDI_Icon_Guide.ai`, as a starting point for creating a PDI icon. This file is bundled with the other samples in the Pentaho Data Integration SDK. You can download the SDK from the [Support Portal](https://support.pentaho.com/home).
---
# 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.pentaho.com/pdia-admin/embed-and-extend-pentaho-functionality-cp/embed-and-extend-pdi-functionality/extend-pentaho-data-integration/create-pdi-icons.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.