Skip to main content
nothanks01
Participant
April 16, 2026
Question

Feature Request: Missing SVG/EPS Export in Adobe Fresco for Vector Workflows

  • April 16, 2026
  • 1 reply
  • 16 views

Adobe Fresco and the Missing SVG/EPS Export Option

Here is the simple version of what I found, and my take on it.

I went looking for whether the Adobe Fresco developers ever gave a real reason why Fresco does not export to a true vector format like SVG or EPS.

What I found is this:

Adobe does not seem to have given a clear, direct public explanation that says, "Fresco cannot export SVG because of X."

Instead, Adobe's docs and staff replies basically point users toward this workflow:

- Create in Fresco
- Open in Illustrator
- Export SVG or other vector formats from Illustrator

So Adobe clearly treats Illustrator as the place for final vector output.

One explanation that often comes up is this:

"Fresco documents can mix vector, raster, masks, and effects in ways that do not map neatly to pure SVG/EPS output."

That sounds reasonable at first, but honestly, I do not think it is a very strong excuse.

My response is simple:

If a document can export cleanly as SVG, then let it export as SVG.
If it cannot, then grey out the SVG option.

That is it.

A lot of software already works like that. It checks the file, and if the file passes the requirements, the export is available. If it does not pass, the option is disabled or the user gets a message explaining why.

So the real issue is probably not that Fresco could never do this.
It is more likely that Adobe chose not to build Fresco that way.

And if you are an artist intentionally working in vector inside Fresco, then you should also understand what is needed to keep the document "clean" for vector export.

That means things like:

- staying on vector brushes
- avoiding raster brushes
- not merging vector with pixel content
- not using effects or masks that break clean vector output

If it passes, it passes.
If it does not, it does not.

That is not confusing. That is normal.
Artists already deal with format limitations all the time.

So to me, the missing native SVG export in Fresco feels less like a technical impossibility and more like a product decision.

In other words:

Adobe could likely have made SVG export available for vector-safe Fresco files, but chose not to, because they want serious vector output to stay in Illustrator.

EPS is a little easier to explain away, since EPS is treated as older and more legacy now.
But SVG is the one that really stands out.

So my final opinion is this:

The "hybrid document" explanation is only partly convincing.
A better user-respecting solution would be:

- enable SVG export when the document is truly vector-safe
- disable it when it is not
- tell the user exactly what is preventing export

That would make sense.
That would be honest.
And that would let Fresco users who are intentionally creating clean vector artwork actually export it in a real vector format without being forced into Illustrator just to finish the job.

That is why I think this is not really about what is possible.
It is about what Adobe wants Fresco to be.
 

    1 reply

    Abhishek Rao
    Community Manager
    Community Manager
    April 16, 2026

    Hi @nothanks01,


    I completely understand where you're coming from here. If you’re intentionally working with vector brushes, it makes total sense to expect a direct export to formats like SVG without needing to move into Adobe Illustrator. I'm sorry for the inconvenience caused due to this not being available in Adobe Fresco at the moment.

    At this time, Fresco does not support native SVG or EPS export(ref: Publish & Export options in Adobe Fresco), and the supported workflow is to open the artwork in Illustrator and export from there. I understand this adds an extra step, especially when your document is already vector-safe.

    If this functionality is important for your workflow, would you mind creating a feature request on our UserVoice page here https://adobe.ly/4cfbzyQ and adding your comments? This really helps our product team understand demand and prioritize improvements, and you'll also receive updates if there's any progress on it. Please feel free to share the UserVoice link here in this thread as well, so others can upvote it.

    Feel free to reach out if you have any questions or need help with anything else. I'll be happy to assist.


    Looking forward to your update.

    Abhishek