Animate Approved Vector Artwork: Keep It Linked or Convert It to Shape Layers?

Two imports, one drawing. In the first, the artwork arrives as linked layers that still answer to the Illustrator file. In the second, the same paths arrive as native shape layers you now own. Both comps animate. At rest they can be pixel-identical, and a still frame comparison will not tell them apart.

The difference lands on a Tuesday, three weeks later, when someone moves a bar six pixels and saves the source.

So the question is not which route looks right. It is which changes are still coming, and which file will own them.

The short answer:

• If the drawing is still being drawn — outlines, offsets, colors, whole elements moving — keep it linked. Transform, parent, retime, and stack effects on linked layers, and every upstream revision arrives without a rebuild.
• If the motion needs the geometry itself — a contour that changes shape over time, a stroke drawing along its own length, points that travel — convert the parts that need that, at a named source revision, and treat the conversion as a fork rather than an upgrade.
• If both are true, split the mark and write down which part belongs to which authority.

Everything else — bounds, anchors, gradients, groups — either confirms that split or makes it messier.

Write down the changes before you choose

Before touching the import dialog, list two things separately.

The motion you have to build. Sort it into transform-level work (a part moves, scales, turns, fades, arrives before or after another part) and path-level work (the shape's contour itself is animated). This is the only honest way to tell whether you need native geometry. A mark that slides, stacks, and settles across a composition is transform work. A mark whose arc visibly redraws itself into a different curve is not.

The revisions you expect. Not "will this import correctly," but "who is going to change what." A moved element and an altered outline matter more to this decision than whether the first preview opened cleanly. If the art director is still circling the offset on one component, you already know the answer for that component.

There is a middle case worth checking before you convert anything for it. If the path animation you need is really a reveal — the artwork appearing along an edge, wiping in, being masked back — a matte or mask on the linked layer can carry that without touching the drawing's geometry. Convert only when the contour itself has to change.

Linked artwork: what the source keeps owning

An Illustrator file imported as a composition brings its layers across separately. That separation is the animation structure, drafted in the source. If two elements sit on one Illustrator layer, one linked layer arrives, and you cannot move them independently without going back upstream. Layer organization in the source is not housekeeping; it is the first pass at your grouping.

The other import decision is sizing. Each layer can keep the full document bounds, or be cropped to its own artwork. Adobe's guidance for preparing and importing still images (helpx.adobe.com) recommends the document-sized option when upstream object positions have to change through Edit Original. The reason is structural: the layer's frame stays put, so the object moves inside it rather than the frame moving with it. A source nudge then reads as a changed picture, and the comp's own transforms are untouched.

That is not a universal recommendation. Cropped bounds give tighter frames and more obvious pivots per part, which is friendlier when each part animates independently. The trade is that placement is now tied to the artwork's extent, so an upstream move is more disruptive. Pick according to what your source is about to do.

Anchors deserve the same deliberation, and a deliberately off-center element is the fastest way to see whether you got it right. Suppose a small rectangle is approved six pixels to the right of the mark's optical center. Rotate that layer around wherever the import put its anchor and the rectangle swings wide, because the part is not centered in its own frame. Nothing is broken; the pivot is just not where the motion needs it. If two parts need different pivots, they are two layers, or one layer plus a group transform. Decide which, by name, before the animation is built on top of the wrong one.

For the common case — the whole mark travels — this barely matters. Parent the linked layers to a null and animate the null. Anchors stay where they were, the source link survives, and Edit Original keeps working.

Worth knowing as history, not as a current defect: a 2018 question on Adobe's community forum, "Importing Illustrator files, not retaining layer sizes," describes layer bounds and anchor placement getting in the way of an animation workflow. That is the shape of the problem in a user's words from that date. It is not a verdict on today's software, and it does not tell you what your version does.

Conversion: what native geometry buys, and what it costs

Converting vector artwork creates a new layer. That single sentence carries most of the decision, because it means the conversion is not a translation of your existing layer — it is a second artifact built from the same paths. The original keeps its link. The copy has native geometry and the shape-layer tools that read geometry: trimming along a path's length, offsetting its points, jittering them, morphing the contour frame by frame.

After converting, inspect the structure rather than the render.

• Grouping. One Illustrator layer can arrive as a shape layer containing several groups and paths. Which group holds what decides whether you can animate a part on its own.
• Transforms. Group transforms can carry an offset that the layer transform doesn't. A converted version that matches at rest can behave differently the first time you rotate or scale something.
• Fills and strokes. Check that they are still adjustable attributes, that colors match, and that weights match.
• Compound paths and masks. A structure that renders as one silhouette may arrive as a group of paths or a path with a hole. Appearance can match while the editable structure doesn't, and the editable structure is what you bought.

Then there are the features. Current Adobe guidance on creating shapes and masks (helpx.adobe.com) describes a newer Illustrator workflow that preserves gradient fills, strokes, and transparency, and excludes freeform gradients and blends. The same page, as of its January 2026 update, still carries older and broader wording about gradients not surviving conversion.

Two conclusions follow, and they are opposite conclusions, which is why the page reads the way it does.

First: stop carrying the rule that gradients are lost. As a blanket statement it is out of date, and it will make you avoid conversion for a reason that no longer holds.

Second: do not adopt the reverse rule either. The support list is per feature and per version. A simple two-stop linear fill and a blend-built glow sit on different sides of it. Test the features this artwork actually uses, on this machine, and write the version number next to the result. The answer belongs to that version.

A mark, three comps, one revision

Set up the following yourself; nothing below was imported, converted, rendered, or revised for this article. What it does is assign responsibilities so that the comparison has something to prove.

Take a fictional mark — call it Halyard — drawn as four layers on one artboard:

• Arc — an open curve, 8 pt stroke, no fill. The part that has to draw on and bend.
• Dot — a 96 px circle with a simple two-stop linear gradient.
• Bar — a 12 × 64 px rectangle, approved with its center 6 px to the right of the arc's optical center.
• Halo — a soft ring built as an Illustrator blend between two circles.

Approved resting state: those four at those offsets, no motion.

Build three compositions. LINKED imports the file as a composition with layers kept separate and sized to the document. SHAPES imports it again and converts the artwork to shape layers; the linked footage layers stay in the comp beneath the converted ones, hidden, so only the shape geometry renders. REF holds the approved artwork flat, purely as a comparison target.

Now split the motion so the asymmetry shows:

In LINKED, animate a whole-layer move. Parent all four footage layers to a null and animate the null's position — the mark rising 40 px and settling. This is motion linked artwork handles without converting, and the null keeps the source link intact.

In SHAPES, animate a path change. Have the Arc's stroke draw on from one end and its curvature ease into the resting shape. This is motion the linked route can't produce without converting.

Be fair about what that proves. SHAPES could also do the 40 px move, and doing it doesn't justify the conversion. The move isn't the reason to convert; the arc's redraw is. And if the arc only needed a wipe, a matte on the linked layer would have covered it and the conversion would be unnecessary.

Move the bar in the source

SHAPES is built at source revision 6. The art director moves Bar six pixels left so it sits on the optical center, and saves the file as revision 7.

On LINKED: Edit Original, save, and the footage updates. Because the layers are document-sized, the frames don't move — the bar moves inside its frame, the null's animation is untouched, and the other three parts are unaffected. That is the documented purpose of the document-sized option, and it is the one step where the choice you made actually shows up. Confirm it on your own file: is the bar in the new place, does every other part hold its position, is the anchor where it was?

On SHAPES: no revision reaches the animated shape layer. The hidden footage underneath still updates on save, quietly, under geometry the comp has stopped reading. What animates holds revision 6 — the bar, the arc, all four parts where they sat when the conversion was run.

You have two repairs, and one of them is a trap. You can repair the copy in place — find the bar's group and move it, or edit its points — and log that the animated layer now carries geometry the source has not agreed to. It is ahead of its own source, not behind it. Or you can convert again at revision 7, which creates another new layer and strands every path keyframe you built on the old one. That stranded layer holds revision 6; the source has moved on to 7; your animation stays where it was. The fresh copy beside it carries no animation at all. The second option looks like a fresh start and behaves like a demolition.

Either way, the comp now has two authorities, and neither branch leaves them agreeing. In the first, the animated layer is ahead of the source and no longer tracking it. In the second, the layer carrying your keyframes is a revision behind the source, and the geometry that matches sits on a copy with no animation on it. Which artifact is stale depends on the repair, which is why the state gets written down. The fork has a birthday.

Reading the comparison

Compare LINKED, SHAPES, and REF at rest, at the extreme of the motion, and at the settle. Then inspect the two features in the mark that sit on opposite sides of the support list.

The dot's linear gradient. The current guidance says gradient fills are preserved; the older wording on the same page says otherwise. The useful question is not which sentence is right but what your version did. Is the dot's gradient a live fill you can still adjust, or a flat color you now have to rebuild? Record the version with the answer, because that answer expires.

The halo's blend. The newer list says blends aren't retained. So the test is not whether it converted — it's what sits in its place and whether that is acceptable. If the halo must exist as native geometry, decide its native form in the file you own, where the artwork is authored, rather than accepting whatever the conversion leaves behind. If you can't make that decision comfortably, the halo is a reason for the halo to stay linked.

Compare at an extreme frame, not only at rest. Gradient direction, stroke weight, joins, and any group offset that only becomes visible once something rotates all hide in the resting pose.

One frame's match proves that one frame matched. The maintenance check is separate: reopen the comp the way you would on a Friday afternoon, make a representative change, and see what it costs. A rendered match does not establish maintainability, and an editable structure does not excuse altered brand geometry. You need both, and they are different tests.

The mixed route, with one authority per part

A split mark is legitimate and often correct — convert the arc, keep everything else linked. What is not legitimate is a split mark nobody has documented, because then two masters exist and the revisions quietly diverge.

Write down which representation owns each part and how shared changes get coordinated. If the arc is converted, then the arc is no longer edited in the source for this shot; if someone does edit it there, they need to know they are editing a reference that this comp has stopped reading. Put the source filename and its revision in the comp name or on a guide layer, so the fork has a label instead of a memory.

It's also worth knowing which way the irreversibility runs. Linking is easy to keep and awkward to convert later without stranding work. Converting is easy to do and, once the path animation is built on it, effectively one-way — those keyframes have no route back onto the linked layers. The expensive mistake is converting early for a preview, then discovering that the drawing wasn't finished.

Choose, then name the owner

The route isn't a setting. It's a sentence:

The mark stays linked at revision 7. The arc is converted, because its curvature is animated over the shot — the draw-on is something the conversion makes convenient, not the reason for it. Any further change to the arc's outline happens in the comp. Any change to the bar, dot, or halo happens in the source and will arrive on its own.

That sentence states the representation, the operations it enables, and who owns the next change. It also tells the next person what they will break.

If you can't write it yet, you don't have a route — you have a first preview that looked right, which is the least informative evidence available.

Frequently asked questions

How should I decide between imported linked artwork and converted shape layers?

By which changes are still coming and which file will own them. Transform-level motion — a part moving, scaling, turning, fading, arriving before or after another part — suits linked layers. Path-level motion, where the contour itself is animated, needs native geometry. If the drawing is still being drawn, or the art director is still circling an offset on one component, that component stays linked. If both are true, split the mark and write down which part belongs to which authority.

Can a matte replace conversion when the artwork only needs to appear along an edge?

Yes, if what you need is really a reveal — appearing along an edge, wiping in, being masked back. A matte or mask on the linked layer can carry that without touching the drawing's geometry. Convert only when the contour itself has to change.

Are gradients and blends preserved when vector artwork is converted?

It depends on the feature and the version. Current guidance describes a newer Illustrator workflow that preserves gradient fills, strokes and transparency, and excludes freeform gradients and blends; the same page, as of its January 2026 update, still carries older and broader wording about gradients not surviving conversion. A simple two-stop linear fill and a blend-built glow sit on opposite sides of that list. Test the features this artwork actually uses, on this machine, and write the version number next to the result. The answer belongs to that version.

What happens to an animated shape layer when the Illustrator source is revised?

No revision reaches it. The hidden footage underneath still updates on save, quietly, under geometry the comp has stopped reading, so what animates holds the revision it was converted at. Repairing the copy in place makes the animated layer ahead of its own source and no longer tracking it; converting again at the new revision strands every path keyframe on the old layer while the fresh copy carries no animation. Either way the comp has two authorities, and the fork has a birthday.

Does a matching rendered frame mean the artwork transferred correctly?

No. One frame's match proves that one frame matched, and gradient direction, stroke weight, joins, and any group offset that only appears once something rotates can hide in the resting pose — which is why the comparison is worth making at an extreme frame, not only at rest. The maintenance check is separate: reopen the comp the way you would on a Friday afternoon, make a representative change, and see what it costs. A rendered match does not establish maintainability, and an editable structure does not excuse altered brand geometry.