PDF Export 'Preserve Illustrator Editing Capabilities' Behavior Change in CC 2023
0 reputation · 20 Jun 2020, 19:28 UTC
0 reputation · 20 Jun 2020, 19:28 UTC
In Illustrator CC 2023, the 'Preserve Illustrator Editing Capabilities' toggle governs how document data is embedded within exported PDFs. While documentation suggests this flag applies specifically to vector content, there is an observed inconsistency regarding how raster effects and hidden layers are handled during the export process.
This behavior is compounded by a shift in default export profiles from 'High Quality Print' in CC 2022 to 'Smallest File Size' in CC 2023, which alters compression and resource accounting. When these PDFs are ingested by external processing services, the resulting hidden layer bloat may lead to indirect connection pool exhaustion on the server side.
Does the flag's scope in CC 2023 truly exclude raster effects from the embedded editing data? Is the inclusion of hidden layers a documented design choice or an inconsistency in the current version's export logic?
The Preserve Illustrator Editing Capabilities toggle does not exclude raster effects from the embedded editing data. Raster effects (drop shadows, blurs, etc.) are always rasterized into the PDF content stream at the document’s Document Raster Effects Settings resolution. When the toggle is on, the original live effect parameters and hidden layer content are stored in private Illustrator data so the file can be reopened in Illustrator with full editability. When the toggle is off, that private data is omitted; hidden layers may still appear in the PDF content stream depending on the active PDF preset.
Hidden layer inclusion with the toggle on is consistent with the round‑trip design intent—preserving the complete document structure for re‑editing—not a CC 2023 defect or inconsistency. The reported default preset shift from “High Quality Print” to “Smallest File Size” in CC 2023 is unconfirmed; verify the active preset in your version. Server‑side connection‑pool exhaustion attributed to hidden layer bloat is an infrastructure hypothesis; PDF content size alone does not directly cause pool exhaustion.
pdftk or Adobe Preflight to see whether hidden layer objects appear in the content stream when the toggle is off.Does your external processing service actually parse and retain hidden layers from the PDF content stream? If it only reads the visible content stream, hidden layer bloat in the private data (toggle on) will not affect it. If it ingests the full PDF including private data, then toggle‑off or a preset that strips non‑printing content may reduce payload size. Confirm this before adjusting server pool sizing.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.