menu
up-caret
down-caret

Figma

Figma is the first collaborative UI design tool built in the browser. Join our growing community and kick off a conversation!

# Feature Requests

We're actively developing Figma. If you have feature suggestions, post them here. Let us know *why* this feature would be important to you.

Trending conversations
Is this color real bad?
@ibnfahmi · 3d
$40 million in the bank 💰💸
@josh · 3d
Bitmap image quality degrading over time
@jchan · 17h
Figma onboarding for developers
@grigoriy · 24h
Why exactly is Spectrum wasting 3/4 of my screen?
@nomadtwin · 14h

Export back to Sketch

October 18, 2017 at 1:11pm

It's more of a workaround right now. Other prototyping tools such as Flinto or Principle only have Sketch import. Would be great to eleminate the need to export individual non-editable png's when I want wo use Figma & Flinto together.

Will ask if Flinto is planning on adding Figma import. :)


February 5, 2018 at 10:18am

is there any way to use my figma designs in sketch?

like-fill
1
  • reply
  • like

February 8, 2018 at 1:00pm

@charan-singh You can export your entire frame as an SVG and open it up in Sketch. You'll have to manually adjust some images which will be missing and texts will be trasformed into filled shaped.

  • reply
  • like

March 3, 2018 at 10:09am

I'm pretty sure Export to Sketch will be a killer feature.

like-fill
15
  • reply
  • like

March 4, 2018 at 5:04pm

Yes would love this too. So that we could design on Figma, and export Sketch files, like for multi design tool UI kits, or different design tools used in a workforce. Or to admit Figma's constraints of features and extensibilities right now, that we could generally design first on Figma then continue it on Sketch for example to animate or prototype your design there with their vibrant extensions ecosystem

like-fill
1
  • reply
  • like

March 5, 2018 at 4:27pm

+1 for Figma –> Sketch export. Only reason I cannot migrate fully to Figma: my client only accepts sketch files. You're better, that's why I'm using Figma, and it should be the case, not because it's hard to go back)

like-fill
9
  • reply
  • like

March 9, 2018 at 12:20pm

With such a feature "All Figma users can FINALLY laverage all those sketch resources & export to clints easely" which would drag the traffic to Figma indeed :)

  • reply
  • like

March 11, 2018 at 1:57am

It would certainly give companies a lot more comfort in jumping to Figma, knowing that they could have that parachute back to Sketch.

like-fill
10
  • reply
  • like

April 3, 2018 at 6:08pm

+1!

The Figma -> SVG -> Sketch is pretty worthless if you're dealing with anything at all complicated. Not to mention the folder structure of a page is entirely unusable and text is outlined! Ouch.

Still have to deliver Sketch files to clients even though we love Figma and using the manual conversion is just not doable.

like-fill
5
  • reply
  • like

+100

like-fill
1
  • reply
  • like

I don't really need this but sounds interesting eitherway and should not be too difficult to implement in my opinion as they already have the Sketch file structure down right? @josh

However, I don't think this will really be on the roadmap right now as importing Sketch is kind a marketing technique to get Sketch users to turn to Figma and not having a "way out" is an "easy" way to keep them that way. As Figma started out, and to some extent still is, as the underdog to Sketch it does not seem like something they would feel the need to implement at this time

  • reply
  • like

I'm really hoping someone will build Figma -> Sketch with our new platform API :)

like-fill
6
  • reply
  • like

@zoink I would, but I don't have time to invest in figuring out the Sketch file format haha

  • reply
  • like

April 13, 2018 at 5:39pm

@zoink +1. I hope someone more capable than I will build the export tool.

  • reply
  • like

April 25, 2018 at 12:42pm

From a business stand point I see it as making little to no sense: spending time and resources building a rival product just to have a ”export to Sketch” option in it.

like-fill
1
  • reply
  • like

May 4, 2018 at 10:18am

+999999 as this is much much needed feature! Please anyone do this magic!!!!!

  • reply
  • like

one of the main reason behind most of clients/companies expect sketch export is for reliability, no matter how fast,fancy,great tool figma is companies won't entrust their entire business, their present-future-past in the hands of another companies cloud platform. i believe an offline tool will put their mind at ease.

like-fill
1
  • reply
  • like

I'm curious how things are perceived by designers - instead of a direct Export to Sketch how about an Export to XML with an additional exporter from that XML dump to Sketch?

That satisfies the need for offline storage plus adds a purely textual intermediate step for hand-edits if anything needed fixing.

I have spent many years in data interchange, often of more complex 3D data with associated geological and chemical scientific data. A "hub-and-spoke" model is much more robust. For example, it allows people to customise a Sketch converter to cope with an older version, so not forcing everyone to upgrade in lock-step.

like-fill
3
  • reply
  • like

If it’s for loss prevention then that seems perfectly fine (as a designer). It would also be appreciated as a first step. But if it’s for “oh I need to move this quickly to sketch for a special plugin” in a common workflow then it could add a layer of clunkiness that wouldn’t be so great.

  • reply
  • like

Considering that Sketch's file format is essentially JSON this should be possible.

  • reply
  • like

@mrbrianhinto possible of course, but it does require diving deep into every aspect of the file format and as far as I know there is no public spec on the sketch JSON structure and possible options.

  • reply
  • like

May 5, 2018 at 4:19am

As I said, I've had a lot of experience in this, and as @liammartens points out, there may be fine details missing in the sketch format.

Something that has irritated me a lot with tools in the Sketch ecosystem is the fragility of the format and how I keep having to either wait for or pay for upgrades on an infrequently used tool. The "use forever" licensing is made a mockery by them so swiftly being broken by new Sketch formats.

Clunkiness can be fixed by an app experience on top that hides the fact that there's a two-step export. Nothing substitutes for a conversion chain being made robust by letting you get in and fix data by hand, or an extra cleanup script.

I guess, looking at the Figma API, it's further proof that JSON has "won" the format wars although for complex data there are a lot of good reasons to use XML as a much more robust format for tooling. JSON has a superficial appeal as being more readable but that actually requires you to keep more semantic understanding in your head, or docs by your side.

like-fill
2
  • reply
  • like

May 30, 2018 at 12:38am

+100 . I designed something in figma only to have some sketch punks wanting the sketch version and now im scratching my head

like-fill
4
  • reply
  • like

July 24, 2018 at 6:48pm

This would be amazing for PDF export as well!

like-fill
2
  • reply
  • like

July 25, 2018 at 6:42am

This would be amazing for PDF export as well!

Yeah! I'm not ready for fully migrate without Sketch and PDF Export options. BTW It's very hard to keep both sources updated.

  • reply
  • like

August 6, 2018 at 1:14am

I'm really hoping someone will build Figma -> Sketch with our new platform API :)

I hope so too even if I think that it should be developped in house. Figma has everything to win to develop such a features and I believe people are waiting for it before switching fully to Figma.

like-fill
3
  • reply
  • like
Show more messages