Graymatter

@Pšenda can pontificate all he/she/they want. For reasons already stated, we need AVIF support. And there is no shortage of people requesting it. See Showing results for 'AVIF'. - Affinity | Forum (serif.com) Serif, please add the ability to import and export AVIF images.

Regardless of @ATP 's objections, I also find the AVIF format a valuable addition to web development. One typical example image I'm looking at right now... Original JPG = 17KB, WEBP = 10KB, AVIF = 4KB. I just now converted the same JPG image to JXL using Affinity Photo 2.2.0. The JXL size = 28KB. Go figure! But this is all moot. The reality is that the only browser supporting JXL is Safari 17.0, which was only released September 26 this year - less than a month ago. Firefox and Opera have had JXL behind a flag for more than two years, and Chromium browsers don't even have that. See https://caniuse.com/jpegxl In comparison, AVIF has wide adoption. In some cases (Chrome) dating back more than three years. See https://caniuse.com/avif So, it would seem that AVIF is not a "new and wondrous formats whose awesomeness often wears off eventually" as @Pšenda suggested. Conclusion: For web development, JXL is currently of no value and looks like remaining so for some time. The AVIF format is useful and beneficial right now. Serif, please add the ability to import and export AVIF images.

+1 on the need for webp export support. AVIF export should also be added. Having read most of the comments on this thread, I'm confused by @LondonSquirrel's dogged anti-webp export stance. Additionally, after reading his post quoted below, I'm curious as to how he could confirm that sites he visited did not use the webp format. Perhaps the sites simply didn't serve webp to him, due to his browser/OS's lack of ability to support them.

+1

Please provide a link to the post you are referring to.

You say that like it's a good thing, something that is acceptable, something that should not surprise us. This is an Affinity forum run by Serif is it not? You say that they do not respond "in principle". What does that mean? Are you suggesting that Serif/Affinity have a company policy stating that they do not or will not reply to comments, questions or request from paying customers? If true, that is a horrible and stupid decision for any company to make, especially a company in the computer software business - an industry where product life cycles are short, new competition is only one geek-with-a-garage away, and customer loyalty is virtually non-existent.

@loukash If you haven't already read this entire thread, please take the time to do so. There has already been plenty of discussion about using other apps/websites to do the conversion from whatever-format to ico. The point is, many Affinity Designer users need and would like the ability to produce ico file output from within Affinity Designer - without having to fuss with other, often poorly written and maintained, software. Additionally, your comment was just not helpful, especially for an Advanced Member. I'm guessing that if @Nate.W is an Affinity user, Nate is more than capable of performing a web search without your assistance. 🖖

It's over 5 years since this topic was started, it has three pages of comments, and not a word from Serif. Someone at Serif/Affinity team needs to chime in here and let us know if this ability will ever be added to the product. Please.

+1 for ico export in Designer.

Hi Lee and thanks for the quick response. Unfortunately this didn't work for me. Firstly, for anyone else reading this thread, the %AppData% shortcut points to "C:\Users\<my user name>\AppData\Roaming" on my PC. So the additional "\Roaming" is not necessary. "%AppData%\Affinity\Designer\1.0\user" is correct. Although this folder does exist on my PC, it does not contain a file named file_export_options.dat. Additionally, the files in that folder have a last modified date of August 2018. This leads me to believe that these files are leftover from the Affinity Designer trial version that I downloaded and installed from the Affinity website last year. I have since uninstalled that version and purchased and installed the version from the Microsoft Store. So, perhaps the question now is... Where does Affinity Designer store the file_export_options.dat file when Designer is installed via the Microsoft Store?

Is there a way to backup and restore my Custom Presets for the Export window? I've made a number of Custom Presets and would like to copy them to my second computer. I'm using Affinity Designer version 1.6.5.123 purchased and installed via the Microsoft Store. Thanks.