Skip to Content
DocumentationTroubleshootingAnalysis issues

Analysis issues

Project analysis is the first step in the rendering process, where Plainly checks the project for any issues that may prevent it from being rendered correctly. Analysis issues occur when an After Effects project uploaded to Plainly Videos fails to be analyzed.

This can happen for a variety of reasons, however a lot of analysis fails are caused by the same things that cause failed renders. It’s suggested that you take a look at the Rendering issues section as well.

Font issuesAsset issuesOther issues
Make sure to read the Intermittent issues guide as well.

Font issues

Please have a look at the Font management section for more info on how to solve font issues.

Missing fonts

If the fonts used in your After Effects project are missing from the provided .zip file, analysis will not succeed. Ensure that all required fonts, compatible with OTF and TTF formats, are properly packaged. The PostScript  names of packaged fonts are case-sensitive and must exactly match the ones used in your project.

Plainly supports variable fonts that contain multiple font styles in a single file.

To check the PostScript name of a font, go to fontdrop.info , upload the font, and check the Data tab.

API error payload example with code WORKER_ANALYSIS_FONTS_MISMATCH

{
  "code": "WORKER_ANALYSIS_FONTS_MISMATCH",
  "message": "Project is missing fonts.",
  "params": {
    "missingFonts": [
      "Poppins-Medium"
    ],
    "extraFonts": [
      "AndaleMono"
    ]
  }
}
From version v0.14.2 extra fonts are deprecated and won’t cause analysis issues.

Duplicated fonts deprecated

If you have duplicate fonts in your project, you will get a failed analysis. Please remove all duplicate fonts from your project, and leave only one instance of each needed font. Then, re-upload the project and try again.

API error payload example with code WORKER_ANALYSIS_DUPLICATED_FONTS_FOUNDDeprecated

{
  "code": "WORKER_ANALYSIS_DUPLICATED_FONTS_FOUND",
  "message": "Duplicated fonts found in zip file.",
  "params": {
    "fonts": [
      "Andale Mono.ttf"
    ]
  }
}
From version v0.14.2 duplicate fonts are deprecated and won’t cause analysis issues.

Unable to parse packaged fonts

Error occurred due to the inability to parse the packaged fonts in the project, probably because some of the fonts might be corrupted. Please replace the corrupted fonts in the project, and try re-uploading the project again.

API error payload example with code WORKER_ANALYSIS_UNABLE_TO_PARSE_PACKAGED_FONTS

{
  "code": "WORKER_ANALYSIS_UNABLE_TO_PARSE_PACKAGED_FONTS",
  "message": "Could not read packaged fonts.",
  "params": {
    "fonts": [
      "Poppins-Medium"
    ]
  }
}

Unable to read project fonts

Error occurred due to the inability to read the fonts from the text layers in the project. Please re-analyze the project or upload the project again.

API error payload example with code WORKER_ANALYSIS_UNABLE_TO_PARSE_PACKAGED_FONTS

{
    "code": "WORKER_ANALYSIS_UNABLE_TO_READ_PROJECT_FONTS",
    "message": "Could not read project fonts."
}

Please have a look at the Font management section for more info on how to deal with fonts and solve any issues.

Asset issues

Missing files

If your project uses asset files (images, video, audio, etc.) that are not included in the .zip file you uploaded, analysis will fail. Please make sure that all the necessary asset files (images, videos, audio files, etc.) used by your project, are included in the .zip file you uploaded.

See Packaging guide for more info on how to solve the issue.

If you have a non-English character in your file name, the errors could happen as well, as the file would be considered missing due to the unsupported encoding.

API error payload example with code WORKER_ANALYSIS_PROJECT_MISSING_FILES_ERROR

{
  "code": "WORKER_ANALYSIS_PROJECT_MISSING_FILES_ERROR",
  "message": "Project is missing files or assets such as images, media files, etc. The assets were not collected or packaged properly.",
  "params": {
    "missingFiles": [
      "/(Footage)/julian-wan-WNoLnJo7tS8-unsplash.jpg"
    ]
  }
}

Unsupported files in a project

Some media formats or files inside your project are not supported by Plainly. These usually fail into two categories:

  1. Unsupported media formats
  2. Unsupported Illustrator / Photoshop files

The error message in the UI will show the After Effects log containing the error message similar to:

Error: After Effects error: Could not read from source. Please check the settings and try again.

Other issues

Unsupported After Effects version

Plainly currently supports After Effects versions from 2023 to 2025. If you’re using a an older version, Plainly will try to auto-upgrade the project to the latest version, however this may not always work. If you’re using a version older than 2023, please upgrade your project to the latest version of After Effects.

API error payload example with code WORKER_ANALYSIS_UNSUPPORTED_AE_VERSION

{
  "message": "Unsupported version of After Effects.",
  "code": "WORKER_ANALYSIS_UNSUPPORTED_AE_VERSION"
}

API upgrade error payload example with code WORKER_ANALYSIS_UNABLE_TO_UPGRADE_AE_VERSION

{
  "code": "WORKER_ANALYSIS_UNABLE_TO_UPGRADE_AE_VERSION",
  "message": "Error occurred due to the inability to upgrade the After Effects project to the latest version.",
  "params": {
    "fromVersion": "AE2022",
    "toVersion": "AE2025"
  }
}
TroubleshootingRendering issues