Raphie

Thanks for your feedback, these are issues that have been logged with our developers to look into and improve the process or resolve the issue.
You can also try putting your adjustments and images in a group and exporting, this has worked for some workflows in the past.

For what it's worth, Apple's Preview.app can convert existing *.icns files to *.ico:
open ICNS in Preview Save As dialog > option-click on the Format popup menu > select Microsoft Icon Doesn't seem to work from a regular PNG or from other formats though.
That's on El Capitan. Your mileage may vary.
Other than that, GraphicConverter can create *.ico files from virtually any bitmap format you'd throw at it. As a user since the 1990s, I can only say that GraphicConverter always comes in handy when everything else may fail, as in: it's not "the best" at anything it can, but it's pretty good at everything. Which is its intended purpose. And it's scriptable, plus it comes with a lot of Automator plugins, so a PNG-to-ICO conversion from Affinity can be fully automated.

I would like this option but really don't need it. I have had to create windows .ICO files that have multiple sizes and different bit depths or windows dev environment will reject the combined file. The app that does this very well and free, GIMP...lol I have this app specifically for making .ICO files.

Gimp is one of the few software that can store multiple icons sizes as a set properly in one ico allowing you to specify different color and compression standards and masking and compatibility levels.  It gets the right binary order for compatibility fallback.  There is no other software that I'm aware of with this level of control and support, and it makes rolling multi-size ico much smaller and more backwards compatible.  whomever implemented that part of their software really knew what they were doing.

Affinity doesn't have to get that technical or fancy, even basic ico support would be greatly appreciated.  same with avif and heic and webp.  it would greatly improve workflow to not be forced to reach to other software for conversions in and out.  I want Affinity to LEAD the modern workflow pack like it did when it was released. ❤️ because they are my favorite tools.

I forgot to come to this post to say thank you for tackling this quickly. I was able to present the final product, and everything looks amazing. Thank you.

Hi @laurent_ginoux,
Thanks for letting me know and I'm sorry to hear this - I will again 'bump' this development report and we hope to have this resolved as soon as possible

Hi @Raphie,
Thanks for your report!
As above, I can confirm this issue is logged with our developers and I have 'bumped' this with your report now - we hope to have this fixed as soon as possible.
I hope this helps

This bug has been noted by the moderators.

Just adding other options. You can also export as SVG, then go to https://Inkscape.org and install this free vector editor, it has the option to Save As (not export) DXF file, which is label in the list as
Desktop Cutter Plotter (AutoCAD DXF file) *.dxf The advantage of using this application is that has other tools that are lacking for the moment in Affinity Designer. Affinity Designer is my main Vector Graphic editor in my work flow, but for example, there are many things I love to do hand drawn, since it give a nostalgic touch for certain projects, and Affinity lacks a way to trace bitmaps.
Inkscape, in my opinion, has one of the best bitmap tracing engine implemented in the application, is a little buggy and takes sometime to get used to it, but once you master it is the best, again in my opinion.
For these rare occasions that Affinity Designer let me down, I can manage by opening Inkscape. It's been around for many years, so I can say with certainty that is secure and amazing tool. Even when I used Adobe Illustrator in the past, Inkscape was my go to for many other stuff. Today I mostly use Affinity Designer, which I love. But again, Inkscape comes to the rescue from time to time.

I know what you mean by not just useful for making favicons. I used to make ICNS & ico files for the apps of the software dev I worked at (and for other apps studios that worked with us), and also, making icon packs to be dowloaded for free for people. Those got to rank to the top (google) for the chains I wanted, hehe😎  .  It was long ago, I'd typically use very specialized apps for that (Photoshop wasn't able to even do just the ico thing well back then (dunno now) and anyway we produced cross-platform, so I needed as well all the ICNS stuff (and back then SVGs/PNGs for Linux, too). I remember having to study both the Windows Vista (and later Windows versions.... till Win XP it had been kindda easier) and Mac OS strict specs to produce both types of libraries, with their design rules. OH. WOW. Just realizing... IcoFX still exists.... Oh, my. Hugely evolved (win, mac icons, but also android, iOS, etc.)
Frankly, I was not aware Gimp could do ico libraries. Nice.
PD: I'd add the feature would be useful as a global one. Both for Designer and Photo. Some have mentioned the technique of just reducing the image from 512x512 (or 1024! I've done such icon sizes) , but that works till an extent; at some point it's extra optimal if one can do pixel art, as at 32x32 and below, it realy is gonna look better if making the by pure pixel art techniques. Pixel Persona has the 1 pixel tool as well, it is just as good as a pixel pusher, would make the deal in Designer for that, but it'd be nice for other reasons to have it also in Photo. Plus... I have the 3 apps, but some people may only have Photo (Photo can be used as a standalone digital painting/illustration/pixel art/graphic design/game art solution, despite being focused on photography and image editing in general).

Is very impressive that there are designers that do not understand that tools for designers need to cover all designers, not only web developers or newbies that know about icons through a favicon web search. Icons are still widely used in many instances and is a profitable business. I find hilarious when people says the new way is better because is new, but the new way is more tedious than the old *.ico file... one file carries all the sizes you added to it, with inherit adaptability to size request.
Every time you submit a power web app, you have to upload dozens of images to do what a single upload would accomplish on an *.ico file. Same on the Apple Store or Google Android Apps, which is ridiculous. That process would be simpler and lighter with probably a new WebM icon file. But since does not exists, haven't done due research to be absolutely sure, you have to upload either one by one or on a compress file. And if you make a change then you have to do the whole process to produce the same list back again. Very ridiculous again in my opinion. Is that the new way you referring to? I'm not sold.
Anyway... Other Possible Solutions
You can use Gimp2 to create icons too. Open source and downloadable tool with pretty other nice tools that you won't find either in Affinity Photo or Photoshop without plugins... for example, exporting *.ico files and creating Normal Maps... among others.
The way Gimp handle it, you start by creating your 256px (like in old days) or larger icon size 512px, and scale that down per layer, and if a layer start looking blurry then you can import your small version or even create them in the same file. Once you have all the sizes you want to cover, Export your layered Gimp file as an *.ico file. Is that easy. Gimp even has an icon previewer if I'm not mistaken, don't quote me on this.
Also, Inkscape has an icon generator integrated. Another open source vector base application, with an icon previewer as well.

Is very impressive that there are designers that do not understand that tools for designers need to cover all designers, not only web developers or newbies that know about icons through a favicon web search. Icons are still widely used in many instances and is a profitable business. I find hilarious when people says the new way is better because is new, but the new way is more tedious than the old *.ico file... one file carries all the sizes you added to it, with inherit adaptability to size request.
Every time you submit a power web app, you have to upload dozens of images to do what a single upload would accomplish on an *.ico file. Same on the Apple Store or Google Android Apps, which is ridiculous. That process would be simpler and lighter with probably a new WebM icon file. But since does not exists, haven't done due research to be absolutely sure, you have to upload either one by one or on a compress file. And if you make a change then you have to do the whole process to produce the same list back again. Very ridiculous again in my opinion. Is that the new way you referring to? I'm not sold.
Anyway... Other Possible Solutions
You can use Gimp2 to create icons too. Open source and downloadable tool with pretty other nice tools that you won't find either in Affinity Photo or Photoshop without plugins... for example, exporting *.ico files and creating Normal Maps... among others.
The way Gimp handle it, you start by creating your 256px (like in old days) or larger icon size 512px, and scale that down per layer, and if a layer start looking blurry then you can import your small version or even create them in the same file. Once you have all the sizes you want to cover, Export your layered Gimp file as an *.ico file. Is that easy. Gimp even has an icon previewer if I'm not mistaken, don't quote me on this.
Also, Inkscape has an icon generator integrated. Another open source vector base application, with an icon previewer as well.

Is very impressive that there are designers that do not understand that tools for designers need to cover all designers, not only web developers or newbies that know about icons through a favicon web search. Icons are still widely used in many instances and is a profitable business. I find hilarious when people says the new way is better because is new, but the new way is more tedious than the old *.ico file... one file carries all the sizes you added to it, with inherit adaptability to size request.
Every time you submit a power web app, you have to upload dozens of images to do what a single upload would accomplish on an *.ico file. Same on the Apple Store or Google Android Apps, which is ridiculous. That process would be simpler and lighter with probably a new WebM icon file. But since does not exists, haven't done due research to be absolutely sure, you have to upload either one by one or on a compress file. And if you make a change then you have to do the whole process to produce the same list back again. Very ridiculous again in my opinion. Is that the new way you referring to? I'm not sold.
Anyway... Other Possible Solutions
You can use Gimp2 to create icons too. Open source and downloadable tool with pretty other nice tools that you won't find either in Affinity Photo or Photoshop without plugins... for example, exporting *.ico files and creating Normal Maps... among others.
The way Gimp handle it, you start by creating your 256px (like in old days) or larger icon size 512px, and scale that down per layer, and if a layer start looking blurry then you can import your small version or even create them in the same file. Once you have all the sizes you want to cover, Export your layered Gimp file as an *.ico file. Is that easy. Gimp even has an icon previewer if I'm not mistaken, don't quote me on this.
Also, Inkscape has an icon generator integrated. Another open source vector base application, with an icon previewer as well.

Is very impressive that there are designers that do not understand that tools for designers need to cover all designers, not only web developers or newbies that know about icons through a favicon web search. Icons are still widely used in many instances and is a profitable business. I find hilarious when people says the new way is better because is new, but the new way is more tedious than the old *.ico file... one file carries all the sizes you added to it, with inherit adaptability to size request.
Every time you submit a power web app, you have to upload dozens of images to do what a single upload would accomplish on an *.ico file. Same on the Apple Store or Google Android Apps, which is ridiculous. That process would be simpler and lighter with probably a new WebM icon file. But since does not exists, haven't done due research to be absolutely sure, you have to upload either one by one or on a compress file. And if you make a change then you have to do the whole process to produce the same list back again. Very ridiculous again in my opinion. Is that the new way you referring to? I'm not sold.
Anyway... Other Possible Solutions
You can use Gimp2 to create icons too. Open source and downloadable tool with pretty other nice tools that you won't find either in Affinity Photo or Photoshop without plugins... for example, exporting *.ico files and creating Normal Maps... among others.
The way Gimp handle it, you start by creating your 256px (like in old days) or larger icon size 512px, and scale that down per layer, and if a layer start looking blurry then you can import your small version or even create them in the same file. Once you have all the sizes you want to cover, Export your layered Gimp file as an *.ico file. Is that easy. Gimp even has an icon previewer if I'm not mistaken, don't quote me on this.
Also, Inkscape has an icon generator integrated. Another open source vector base application, with an icon previewer as well.

Is very impressive that there are designers that do not understand that tools for designers need to cover all designers, not only web developers or newbies that know about icons through a favicon web search. Icons are still widely used in many instances and is a profitable business. I find hilarious when people says the new way is better because is new, but the new way is more tedious than the old *.ico file... one file carries all the sizes you added to it, with inherit adaptability to size request.
Every time you submit a power web app, you have to upload dozens of images to do what a single upload would accomplish on an *.ico file. Same on the Apple Store or Google Android Apps, which is ridiculous. That process would be simpler and lighter with probably a new WebM icon file. But since does not exists, haven't done due research to be absolutely sure, you have to upload either one by one or on a compress file. And if you make a change then you have to do the whole process to produce the same list back again. Very ridiculous again in my opinion. Is that the new way you referring to? I'm not sold.
Anyway... Other Possible Solutions
You can use Gimp2 to create icons too. Open source and downloadable tool with pretty other nice tools that you won't find either in Affinity Photo or Photoshop without plugins... for example, exporting *.ico files and creating Normal Maps... among others.
The way Gimp handle it, you start by creating your 256px (like in old days) or larger icon size 512px, and scale that down per layer, and if a layer start looking blurry then you can import your small version or even create them in the same file. Once you have all the sizes you want to cover, Export your layered Gimp file as an *.ico file. Is that easy. Gimp even has an icon previewer if I'm not mistaken, don't quote me on this.
Also, Inkscape has an icon generator integrated. Another open source vector base application, with an icon previewer as well.

Hi. I tried the collect solution via Resource Manger and it's not the same.
Look, lets' all be honest. We all need the same functionality that the "Package" has in InDesign. No "do this and then it asks you for that" type of thing. Just the same thing. We don't want Affinity to try and re-invent the wheel.
The reason is that is the way professionals need their files handled. Full stop. You may think it's overkill or not a big deal, but if you're dealing with many staff (and some freelancers who have differing amounts of experience), you need a proven system that will work -- even after a year or more where the original machine might have been reformatted or changed.
I'm not sure if it's legal concerns preventing this seemingly straight-forward feature but perhaps they don't want to raise the anger of Adobe, but that's what the pro market needs.
 

That is an excellent reply.  This coming from a Ai user for years and now considering AD.  I use Ai for laser cutting as well.  Taking the extra step of converting to dxf aint a biggie for now.

My feature request is for Affinity Publisher to have the ability to create form fields to be filled in ... in order to create fillable form PDF to be filled and edited in other software programs if needed.  I would love to do this in order to make my patients process of filling our paper forms easier, for example to be done on an iPad.

This was asked before.
I include a screen capture of all the options available in the Find & Replace and Select dialog from FreeHand.
It was great to have something like this :-)

Can be a great timesaver when you open documents from someone else or from CAD applications. Change any attribute a thousand times at once with only a few clicks.

This is really a bad solution, a proper packager should be in place, especially if Affinity Publisher still need to maintain the images embedded to preview, even if it says they are linked. And as you point out this works with a fairly large file, almost a Gigabyte. But I wonder how this going to behave with even larger files. Photoshop itself won't handle properly over 5 Gb, I always test to see how far I can go with a software since the computer is more than capable that kind of file size in memory. The funny thing is that even Microsoft Publisher, the most basic publication application has this feature.
Not to have a proper packager is a huge mistake, the reason you create publications is mostly to send to print, most digital printers are OK with a PDF file but most reputable printers prefer to have the original file. They are dealing with thousands of prints per day and their schedule is tight as Air Control on an Airport, a small delay because of an error on a PDF can cost millions of dollars in delays, with the original file they can make adjustments on the fly.
And I don't know if any young freelance know this, fonts are software and many printers do not have the time to update their font catalog, because they probably have the font in the system doesn't mean is the same font, and what they look in the screen is nothing close to what you see in your screen. And the PDF will used the font installed in the system is currently open, fonts are not saved with the document. Try to print a PDF file from the web that uses licensed fonts and you will see what I mean by this. Of course, this is only one variable from the many could go wrong when moving a design to another computer on an alien network.
And this is very true, if you have been in the business for as long idyguy, I'm almost getting there, not any reputable firm will take seriously Affinity Publisher without this feature. This should be your higher priority. Right now I have to have a meeting and back up everything I suggested to my agency of considering Affinity Publisher as a replacement for InDesign, it is that serious.

Chris_K wrote:
Future? Not bad? That’s outrageous and absolutely unacceptable! Here’s why:
I’ve been working with QuarkXPress since the 90s and InDesign since the 2000s. I was completely surprised when I noticed a Package / Collect for Output feature was missing. So I made a call to a project manager working with various commercial publishers and with contracts at CocaCola, HP, Cannon, Honda, Hallmark, etc.
The basic response was:, “What! There is no way that output process will work or be taken seriously by anyone in ‘The Industry.’”
So Chris, I’d respectfully suggest that instead of moving this to a feature request and thinking about it as something for a future update, Serif get on this immediately and have it working prior to the first release.
And while I understand there is little chance Serif will take my advice, I’ll predict this is one of the biggest blunders ever. Whoever vetoed the Package / Collect for Output feature has little understanding of the final output process of professionals and commercial print houses.
yYM
- - - - - - - - - -
AFFINITY PUBLISHER (BETA) 1.7.0.133
- macOS: 10.13.6
- MacBook Pro (Retina, 13-inch, Early 2015)
- Processor 3.1 GHz Intel Core i7
- Memory 16 GB 1867 MHz DDR3
- Graphics Intel Iris Graphics 6100 1536 MB
 

The Big advantage of Packaging is, that you
can find all used Content, wherever it is on your Network, and the Packagingprocess sorts out all unessesair Content that you have put to your Contentfolder but didn´t use in your final layout..  When you Package a Dokument and send it to a partner ore collegue using also afinnity publisher,  either way, you need to send many data to him..  from filesize there wouldn´t be a big differenze if you put the used content to a folder or if you embed the content to your afpublisher Document.
So i would suggest to embedd all the used contend to your document and send it this way..  But i would suggest a further Feature here !!!
 
using the embedded objects in the Ressource Manager..  give us the option to Export the embedded Content to a Folder we point to !
 
This of course wouldnt work when exporting to idml format which also is essential for many companys that work together with external partners..  My Architecural Company does this all the time ..  sharing indesign documents or idml formats with for example the greenplaners..    So i assure you we need this workflow..
I dont know how afpubisher would handle the export of idml files and the packaging of content when it will support idml..  i hope they find a good solution for this.. 

I third that packaging files is important for a page layout app!