Question
Illustrator automation scripts: 2023 GPU Performance default creates headless compatibility boundary
Ari Echo
0 reputation · 29 Mar 2023, 12:43 UTC
45K views1
Loading…
0 reputation · 29 Mar 2023, 12:43 UTC
Scripts that execute in a local Illustrator desktop session may fail when the same automation is moved to production build agents that run without an attached display or user session. Running ExtendScript automation for batch PDF and SVG exports inside a CI/CD pipeline requires a supported headless execution path.
Illustrator requires an active user session with a display server or interactive window station to initialize its UI subsystem, even when driven solely by scripts. Adobe does not provide a supported headless mode, server-side API, or Docker image for Illustrator as of the 2024 release cycle; InDesign Server is the official server-side vector alternative. The 2023 release enables GPU Performance by default, adding a compatibility boundary in virtualized environments lacking GPU passthrough. Workarounds such as Xvfb on Linux or Windows interactive services remain unsupported and break across OS and Illustrator upgrades.
Practical verification involves running a minimal ExtendScript on clean CI agents without a virtual display to characterize the failure, though symptoms vary by OS and version. Font licensing and activation state also differ between local and production machines, causing substitution that changes layout and export output.
The unresolved question is whether Adobe will ever provide a supported headless execution mode for Illustrator, or whether automation teams must permanently maintain fragile virtual-display configurations or migrate vector processing to alternative libraries such as Paper.js or Skia.
Is there any documented configuration for running Illustrator automation scripts in a headless CI/CD environment as of the 2024 release cycle? How should the 2023 GPU Performance default be handled on build agents without GPU passthrough? What migration boundary is appropriate when the interactive session requirement makes server-side Illustrator automation unsupported?
34775 reputation · 29 Mar 2023, 15:13 UTC
As of the 2024 Adobe release cycle, there is no officially documented headless execution mode for Illustrator automation. Scripts driven by ExtendScript must run within an environment that presents an active user session with a display server or interactive window station. Adobe does not provide a supported headless mode, server-side API, or Docker image for Illustrator.
The 2023 release enables GPU Performance by default, which causes Illustrator to request GPU resources during initialization. In headless CI agents without GPU passthrough or a virtual GPU, this request can fail or produce initialization errors, creating a compatibility boundary between the 2023 default and display-less build environments.
illustratorFile > Preferences > Performance and uncheck GPU Performance.xvfb-run on Linux or a Windows interactive service), keeping in mind these configurations are fragile.To determine whether disabling GPU Performance alone suffices or if a virtual display is still required, could you share which operating system and Illustrator version the CI agents target? This detail changes the recommendation.
sha256sum) to confirm visual and metadata consistency.Use comments to ask for clarification. Post a solution as an answer.
34,775 reputation · 29 Mar 2023, 17:42 UTC
While Illustrator’s ExtendScript engine still requires a UI session, the 2023 GPU Performance default can be turned off without a full virtual display. On macOS you can edit ~/Library/Preferences/com.adobe.illustrator.plist and set GPUPerformanceEnabled to false; on Windows edit the corresponding Adobe Illustrator Prefs.ini or set the environment variable ADOBE_GPU_PERFORMANCE=0 before launching Illustrator.exe. This removes the GPU request and lets the app start on a headless agent that only has a basic X server or none at all. It’s a lightweight, version‑agnostic workaround that keeps the same script logic while avoiding the fragile Xvfb or Windows service setups.