A lot of times I exclusively need to export in WebP. I have used TinyImage, which is quite good, but have you seen their pricing?
Plugin pricing and the “eternal subscription” model has become obscene. While I’ve seen other larger app-like plugins with a higher cost, everyone should know that this plugin actually costs more than the entire Figma platform itself minus FigJam, both monthly and yearly (as of today December 2, 2022).
Monthly $19 x 12: $228
Figma monthly $15 x 12: $180
Yearly [$14 x 12]: $168
Figma yearly [$12 x 12]: $144
The other issue is the AUD conversion, which means if you’re in the US you’ll pay more than the listed price. I made the mistake of signing up for TinyImage in August (when it was $15/mo) and was charged $15.87 and $15.62 for August and September (this may be Paypal-specific but regardless, it does occur), and have canceled.
So yes, let’s get WebP as an export format (with a quality/compression value).
The plugin for WebP images is annoying and overly complicated. This is the one missing feature that makes me want to return to Sketch. WebP support is necessary to be a competent tool for the modern web. It’s frustrating that the capability isn’t native.
This is crazy that this has not been responded to by @Figma_Support. This should be one of the easiest things to implement, especially as there are plugins that do it, and they only have access to the API.
Another problem with TinyImage besides the steep cost for exporting is that its webp implementation I think is flawed: it appears to compress a webp only after exporting it first as a png and the quality setting effects both the png quality as well as the webp compression. So, when you lower the quality from 100% (which you should in most cases) the output gets degraded both at the png step and the webp step.
Whereas if you instead export as png directly from Figma to files, then run those files through a 3rd party converter (several have been mentioned in this thread), you can get a higher quality webp image for the file size than doing so with TinyImage.
Bumping this because it should be really straightforward to implement. As an engineer it sucks to have to do that extra step of converting the image for the sake of optimizing network usage, and I’m sure that adding support for it wouldn’t be a big deal engineering wise.
I wonder how it is possible that an application for digital product design does not allow to export the resources in WebP format.
It’s such a basic and necessary functionality right now that I don’t understand why we have to beg them to added.
And the saddest thing is that there is not even a response from someone from @Figma_Support in this thread. They make me think that writing here means wasting my time.
I’m literally in the process of using ChatGPT to help me make a plugin for good webp compression exports. Asking it to help me create it so there is no cost and I can lunch it as a free plugin 😅
It should be the platform’s number 1 priority. Since the format has been widely accepted for a long time, many other more basic tools already have this option native.
If the Figma team is looking for a good compression engine, the one that https://webp-converter.com/ uses is the best I’ve tried.
Related to this, it would be wonderful if the built-in exporter for jpg, png, svg, and pdf would utilize “tiny” engines. The default output from Figma is usually very compatible but often several times larger in file size than it could be.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.