> For the complete documentation index, see [llms.txt](https://developer.eagle.cool/plugin-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.eagle.cool/plugin-api/plugin-review/criteria/visual-assets.md).

# Visual Assets

The plugin icon and covers are the first visual information users receive. Each icon and localized cover is reviewed to confirm that it is present, clear, relevant, and not misleading.

We evaluate whether assets communicate the plugin successfully; we do not require every plugin to share one visual style. Personal aesthetic preference or a belief that an asset could be more polished does not independently justify rejection.

## Overall Consistency

The icon and covers may use different compositions, but their color, visual language, and product identity should work together. Localized covers may use different text, but they must not present conflicting functionality or product identities.

Each locale is reviewed independently. A correct cover in one locale does not establish that another locale is acceptable.

## Plugin Icon

The icon should:

* use a square canvas with a complete, intentional icon composition;
* leave visible safe space between the main graphic and canvas edges so important content survives Plugin Center rounding or cropping;
* have a reasonable relationship to the plugin's name, function, output, or concept rather than using an arbitrary generic symbol;
* remain recognizable at small Plugin Center sizes with clear contrast and focus;
* avoid visible stretching, compression, major cropping, or fragmented graphics.

An opaque app-icon background and the [official icon template](https://www.figma.com/community/file/1301113485954941759/eagle-plugins-icon-template-english-version) are recommended, not mandatory. Transparent corners, transparent backgrounds, and other visual styles may pass when the composition is coherent, safely padded, relevant, and recognizable.

The icon must not impersonate an official Eagle plugin or clearly copy a known third-party brand. Ordinary assets are not automatically rejected merely because ownership cannot be independently investigated, but developers remain responsible for obtaining the necessary rights.

## Plugin Covers

Covers should help users understand the plugin quickly. Acceptable approaches include:

* screenshots of the actual interface, workflow, or output;
* diagrams that accurately explain real behavior;
* relevant illustrations or composite layouts that do not mislead users.

Real interface screenshots often provide the clearest evidence, but they are not the only acceptable format. Decorative artwork, generated imagery, and AI-assisted design are not rejection reasons by themselves. The visible result must be relevant and must accurately represent functionality available in the current release.

Covers must also:

* keep the subject, interface, and required text understandable at Plugin Center card sizes;
* use a clear focal point and a background that does not interfere with comprehension;
* avoid visible stretching, compression, major cropping, unexpected black bars, or filler areas;
* avoid presenting imagined interfaces, outputs, or features as real product capabilities;
* avoid dense paragraphs, long feature lists, and essential text that becomes unreadable when reduced.

Minor cropping of nonessential interface edges, scrollable content, or decoration does not block a submission while the core function remains clear. A cover is not rejected merely because it lacks a polished frame or extensive decoration.

Use the [official cover template](https://www.figma.com/community/file/1302217259099110218/eagle-plugin-introduction-template) as an optional composition reference.

## Common Reasons a Submission Does Not Pass

* A required icon or localized cover is missing.
* The icon is not square, or important content is cropped at display size.
* The icon is unrelated to the plugin or unrecognizable when reduced.
* The icon or cover is visibly stretched, compressed, severely cropped, or padded with unexpected black bars.
* The cover's subject or required text cannot be understood at actual display size.
* The cover presents an interface, feature, or output the plugin does not provide.
* Localized covers conflict with one another or use the wrong language.

Corrections should address visible issues—for example, export at the correct aspect ratio, add safe space, use the actual interface, or remove unreadable text. “Make it look better” is not actionable review feedback.