Skip to content
← Adobe XD: Feature Requests (Read-Only)

Request details

Adobe XD: Feature Requests (Read-Only): 01 : Design mode

Categories

(thinking…)

Image component instances are a reference to reduce file size

When it's necessary to place the same image many times throughout a document, it should be possible to create a master component that stores the heavy data so that the instances can reference it. The instances would only use a small amount of disk space.

I was surprised to find that XD does not utilize such optimization.

When designing a small portion of a larger environment (eg a plug-in for other software) I'll often just use a screen shot for context. This means one or a small set of screen shots will be used many times throughout my document. Instances that reference the master data would dramatically reduce the size of these files.

1 vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

plainclothes shared this idea  ·   ·  Report…  ·  Admin →
action-required  ·  AdminElaine (Adobe) (Product Manager, Adobe) responded  · 

Thanks for getting back to us. We had a developer look at it yesterday, and we were also unable to reproduce it on our side. Thanks for reporting this, and if you see issues like this in the future, please do reach out on the Community Support forums, where you’ll get a quicker response from our support team. https://community.adobe.com/t5/adobe-xd/bd-p/xd?page=1&sort=latest_replies&filter=all

Show previous admin responses (1)

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • plainclothes commented  ·   ·  Report

    Looks like there's an issue with one of my files.

    I just tried this on a smaller design where it was easy to see the file size incrementing. In that file, minimal overhead is added whether I dupe the image on it's own or as a symbol. In the original file that triggered my request, it's still bloated.

    I'll just move on and stop worrying about that one.

  • plainclothes commented  ·   ·  Report

    If this statement were true:
    "As Elaine mentioned, XD refers to a single image even if it is used multiple times"

    I would expect to see minimal incremental file size increase when placing multiple instances of one image. I wrapped mine in a symbol, since that seemed like the logical way to invoke efficiency.

    File size increases arithmetically with each placed instance, whether the image is in a symbol or not. I just modified and resaved the file in question after updating XD again to no avail.

    I'll try again with a fresh file when I have time, but testing XD is not what I get paid to do. I'm surprised the XD team is still relying on it's users to test basic features like this. Maybe it was a regression, maybe it never worked. That's something your team should be able to answer pretty quickly.

  • Anirudh Sasikumar (Adobe) commented  ·   ·  Report

    As Elaine mentioned, XD refers to a single image even if it is used multiple times in the document (inside or outside a component).

    Publishing that component to CC Library will create a non-referential copy of the image inside the CC Library element (XD's internal model is still referential). There were inefficiencies in that area prior to XD 42; editing main and re-publishing to CC Library will let you take advantage of the fixes here.

  • plainclothes commented  ·   ·  Report

    Should I expect the change to impact existing files?