I do not want my file to be copied. I just want the file that I share to export that can then also be exported.
I need more options.
If I create a export the is possible.
2 Likes
What would be the point of disabling copying in this case? Someone could export individual assets as SVG and paste them into a new file if they wanted.
1 Like
Thanks for your message 
If the other person can copy the file. They have the file and I donāt want that. I just want her to be able to export the images.
1 Like
But whatās the use-case for this? Usually this restriction is used as a safety feature so others canāt steal your work easily, but allowing them to export things will make it super easy to do that. So if itās not a safety feature, what is it for?
1 Like
We as a designer cooperate with external developers. We do not want these developers to be able to save or export the whole file. Only what they need. Because we have spent a lot of time to create the file.
2 Likes
A lot of these sorts of requirements are very much edge cases. I can see the reverse being a problem forever getting slacked by the developer because I forgot to put an export on X. The easy fix is to just create a file with just the exports in it.
1 Like
Thereās a degree to which this, or similar requests, might be read more as trying to make dev hand over easier, more straightforward.
At the moment a dev is somewhat left to their own devices in working out which elements to export ā it may not be obvious to them that X icon needs to be exported by selecting Y parent container, that subtly adds extra padding, handles baseline shift/text alignment etc etc.
Sure, manually adding red-lines and instructions can help, but in a fast-moving, small team thatās not always feasible, or kept up-to-date.
So, some means of āfilteringā for devs, to see just those elements with Export settings could be useful.
Part of this puzzle might be helped if I could set export properties on Components once, and have that value passed through to all instances thereof ā would anyone agree with that approach?
5 Likes
Exactly it would be great what you can share.
Another case I just encounterā¦
We have taken/invested time to produce a great and complete UI kit.
We start all our project with it.
We also work with a lot of other agencies as creator of the design system for common customers.
And this morning, I just learn that one of our main competitor is duplicating our starter UI kit since 1,5 year without telling us for his own clients. I donāt find this fair !
This option can solve the problem.
And I know there is a lot of free UI kitā¦ so they have to use those
3 Likes
Sorry to hear that. 
Any news about this feature implementation?
In our team we moved to figma also because we are trying to merge all the activities and deliverables in one platform. Actually the only solution for sharing project is to use Zeplin, otherwise the copy function let the client to copy the whole file on a local copyā¦
1 Like
Iām facing the same problem
I work with external client with ācan viewā access and I want them to be able to export assets/screens/whatever they need, but not be allowed to copy or share the files
I agree with Marc_Notrop 's observation that developers donāt know what they really need to download (the layout of the icon only, or the icon and its area?).
So his suggestion might be a good compromise, i.e. that itās up to the design team to decide what can be downloaded or not. And above all, that this permission parameter can be kept on the instances.
This feature would be really important: Allow viewers to export all assets from the file but not allow to copy the file and design itself. Designer teams put a lot of effort to create the components, auto-layouts, etc and donāt necessary want to share that with someone else.
1 Like
Please, @figma listenersā¦
Hear us about this problem !
Iām pretty sure this doesnāt cost you a big effort
and doesnāt compromise your business model.
To all here, keep the subject live 
As a Product Designer, we are always encounter copyright problem to our Design Works in the file that could just easily be duplicated by others. As a matter of fact itās about to keep our Design File save from others to just share it without our permission.
So thatās why Iād suggest to Enable the File Owner to also prevent Editor from Copy/Duplicate File, and export or save File as.fig. Not just to Viewer.
Iāve been a Pro Account user for some time and feel that this is crucial for us to always keep our File save no matter what.
Thank you for having me in this platform and letās discuss together 
15 Likes
Completely agree! Allowing this feature to be built in will especially be useful in scenarios where someone hires an expert Figma freelancer to help build out their IP/vision/concept.
1 Like
There should also be a feature to prevent the editors and viewers to share the file further.
Currently editors are allowed to add more editors and viewers and at the pro account level we have an admin who is looking into access management. So this feature will be helpful.
4 Likes
Canāt agree more!
2 Likes
this is long overdue! please add this feature. I want my clients to export assets, but not just copy the full file.
4 Likes