Skip to main content
H
Honmeg
Participant
July 17, 2026
Answered

How Do I Install my Own ZXP plugin

  • July 17, 2026
  • 1 reply
  • 87 views

Hello, I need some assistance with Making my own plugin for Illustrator. I have been following the documentation and have my folder set up as below, I am able to sign and create the ZXP file via powershell, but when i go to install via ZXPinstaller or extension manager, i get an error “failed to install, status = -410! ” This error seems to point to an issue with the file structure when signing the ZXP, but I’m pretty sure I’m doing it correctly. My plugin is a tool that allows the user to Select a number of points or a line and generate an Elepse that best fits them. 

The signing code:
.\ZXPSignCmd.exe -sign "C:\Users\name\Downloads\com.atsuji.ellipsefit.panel" "C:\Users\name\Downloads\EllipseFitPanel.zxp" "C:\Users\name\Downloads\cert.p12" Password

File structure:

 


Any assistance on this would be awesome. I attempted to previously make this as a ZSX script, but ran into limitations with what i could do due to incompatibility around the numeric.js file.

I suspect tits an issue with the Manifest so i posted it below as well. I’m on the moist current version of Illustrator via Creative cloud

<?xml version="1.0" encoding="UTF-8"?>
<ExtensionManifest Version="7.0"
    ExtensionBundleId="com.atsuji.ellipsefit"
    ExtensionBundleVersion="1.0.0"
    ExtensionBundleName="Ellipse Fit Panel">
 
  <ExtensionList>
    <Extension Id="com.atsuji.ellipsefit.panel"/>
  </ExtensionList>
 
  <ExecutionEnvironment>
    <HostList>
      <Host Name="ILST" Version="[17.0,99.9]"/>
    </HostList>
    <LocaleList>
      <Locale Code="All"/>
    </LocaleList>
    <RequiredRuntimeList>
      <RequiredRuntime Name="CSXS" Version="8.0"/>
    </RequiredRuntimeList>
  </ExecutionEnvironment>
 
  <DispatchInfoList>
    <Extension Id="com.atsuji.ellipsefit.panel">
      <DispatchInfo>
        <Resources>
          <MainPath>index.html</MainPath>
          <ScriptPath>panel.js</ScriptPath>
        </Resources>
        <Lifecycle>
          <AutoVisible>true</AutoVisible>
        </Lifecycle>
        <UI>
          <Type>Panel</Type>
          <Menu>Ellipse Fit</Menu>
          <Geometry>
            <Size>
              <Width>260</Width>
              <Height>200</Height>
            </Size>
          </Geometry>
        </UI>
      </DispatchInfo>
    </Extension>
  </DispatchInfoList>
 
</ExtensionManifest>
    Correct answer M. Ufuk Korkusuz

    Hi,

    At first glance, the manifest itself looks fine, so I don’t think that’s the primary issue.

    Error -410 usually means the installer considers the package to be an invalid ZXP, so I’d start by checking the package structure rather than the manifest itself.

    One thing I’d verify is that your manifest.xml  is inside a CSXS folder. CEP extensions expect a structure like

     

    com.atsuji.ellipsefit.panel/
    CSXS/
    manifest.xml
    İndex.html
    panel.js
    numeric.js
     

    Also make sure you’re signing the extension’s root folder, not its parent directory.

    If your structure already looks like this, could you share the complete folder tree before signing? That would help narrow down whether the issue is with the package layout or the signing process.

    1 reply

    M. Ufuk Korkusuz
    M. Ufuk KorkusuzCorrect answer
    Participating Frequently
    July 18, 2026

    Hi,

    At first glance, the manifest itself looks fine, so I don’t think that’s the primary issue.

    Error -410 usually means the installer considers the package to be an invalid ZXP, so I’d start by checking the package structure rather than the manifest itself.

    One thing I’d verify is that your manifest.xml  is inside a CSXS folder. CEP extensions expect a structure like

     

    com.atsuji.ellipsefit.panel/
    CSXS/
    manifest.xml
    İndex.html
    panel.js
    numeric.js
     

    Also make sure you’re signing the extension’s root folder, not its parent directory.

    If your structure already looks like this, could you share the complete folder tree before signing? That would help narrow down whether the issue is with the package layout or the signing process.

    Typography • Type Design • Illustrator Scripting • Open Source
    Firefly Community Gallery
    Adobe Firefly

    Remix with Firefly Community Gallery

    Thousands of free creations to fall in love with and remix in Firefly.

    Explore now
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices