DESIGNER - keep groups together when import

[rulo]

keep groups together when import files from Ai or PDF like freepik.

[walt.farrell]

Does PDF have the concept of a "group"? I don't think it does, and if not, then there's no way to do what you suggest. 

[rulo]

Yes you are correct. my mistake.  but Ai files and EPS files from freepik or others websites if you open it in illustrator, vector or shapes are in groups if the designer puts together, but when import to Affinity Designer it dissapear groups and is one by one shape or vector and its a pain try to move some vectors with out touch others.

[MikeW]

3 minutes ago, rulo said:

Yes you are correct. my mistake.  but Ai files and EPS files from freepik or others websites if you open it in illustrator, vector or shapes are in groups if the designer puts together, but when import to Affinity Designer it dissapear groups and is one by one shape or vector and its a pain try to move some vectors with out touch others.

That it works in AI is when there is an embedded .ai file in an .eps. Obviously, an AI file opens as per the designer created it.

When one opens an AI file in an Affinity application, it is only the embedded .pdf file that is opened. 

[lacerto]

20 hours ago, walt.farrell said:

Does PDF have the concept of a "group"? I don't think it does, and if not, then there's no way to do what you suggest. 

PDFs have "group"-like capabilities and behavior but terminologically they are "ContentStreams" and "Optional Content Groups" (the latter also called as "PDF Layers", which can be global within a PDF document). It is possible to create page-wide ContentStreams, select them individually, change their Z-order, combine and delete them, set OCG visibility, printability, etc.

Perhaps this extract from Foxit Quick PDF Library SDK documentation clarifies somewhat the terminological confusion (which is further complicated by the functional difference "layers" have in Affinity vs. Adobe apps):

Quote

With Quick PDF Library, we support Adobe’s Optional Content Groups (called layers within Acrobat and Adobe Reader) and also our own Quick PDF Library Layers.

What’s a Quick PDF Library layer I hear you ask?

Well, a page has one or more content streams. These are combined into one long string by a PDF viewer. When Quick PDF Library was first developed we called these content stream parts "layers" as they enabled you to move groups of things on top of and below other things. All the “layer” functions in Quick PDF Library work on these content stream parts.

In the 1.5 PDF specification, Adobe added Optional Content Groups. Unfortunately, within Adobe Acrobat and Adobe Reader, they decided to refer to these OCGs as Layers. You can access these within the Layers tab.

It's unfortunate that we have these conflicting terms – in the future, we will probably look to make some adjustments in Quick PDF Library to eliminate the confusion, however, for now, you will need to pay careful attention when working with these functions.

UPDATE: As an example of group-alike behavior of content streams, here is how Adobe Express opens a PDF page containing two of them (initially groups within Adobe Illustrator but saved as PDF without AI content), which show as two "groups" already when edited in Adobe Acrobat Pro, but here also terminologically "grouped" (and ungroupable/regroupable objects, which can be edited much as any regular group objects in any design app), and which can subsequently be saved back as a PDF once "edited and enhanced" in Adobe Express (but losing again the conceptual grouping information and meta data when saved back):

In Adobe Acrobat (CC2025), when editing the content:

...and in Adobe Express, when choosing "Use design tools" in Adobe Acrobat:

UPDATE: Affinity apps actually utilize OCG (optional content groups) specifically as page-specific groups. This is achieved by adding a "Layer" layer in the document, and then exporting to PDF so that layers are included. In Adobe Acrobat, the user can then show and hide page-wise these individual "groups" as Adobe layers. Serif has also implemented a feature where these optional content groups are read back in Affinity apps as "Layer" layers, thus utilizing a PDF feature as a way to smuggle in proprietary document information and hierarchy. Other apps reading PDFs do not support this Affinity implementation, which in a way converts a limitation (lack of global layers) into a beneficial feature (page-specific grouping).

layer_based_pdf_grouping.afpub

affinity_layer_layers_as_page_specific_groups.pdf