1)\u000aOne credit is one icon generation?\u000a\u000a2)\u000aCan .ico file be created with different resolutions?\u000a\u000a3)\u000aIf question 2 is not possible, is there any chance you might add this in your process?\u000aFor example, run imagemagick on your server, imagemagick can generate images, so when the image is generated through AI then imagemagick (or something similar) could create a .ico file with different resolutions without having to use the AI service. You just have to set it up on your server. Off course the user could do it but as an service to the user (and convenience) having an .ico ready would be really nice. \u000a\u000a4)\u000aCould you consider the following:\u000aUse the leftover credits of each month to auto\u002Dgenerate different icons and put those for download for all subscribed users. Those icons could then serve as an sort reserve icon repository open for all subscribed users. This gives more bang for bucks and it always stays withing the processing quota (you use the UNUSED credits of the users at the end of the month). Within a short time you could create a gigantic library. It also can become an extra incentive for new users to get an subscription. You don\u0027t have to use all credits in the beginning, you could begin with 20% of it and see how it effects the service and increase as the months go by.

Question

1)\u000aOne credit is one icon generation?\u000a\u000a2)\u000aCan .ico file be created with different resolutions?\u000a\u000a3)\u000aIf question 2 is not possible, is there any chance you might add this in your process?\u000aFor example, run imagemagick on your server, imagemagick can generate images, so when the image is generated through AI then imagemagick (or something similar) could create a .ico file with different resolutions without having to use the AI service. You just have to set it up on your server. Off course the user could do it but as an service to the user (and convenience) having an .ico ready would be really nice. \u000a\u000a4)\u000aCould you consider the following:\u000aUse the leftover credits of each month to auto\u002Dgenerate different icons and put those for download for all subscribed users. Those icons could then serve as an sort reserve icon repository open for all subscribed users. This gives more bang for bucks and it always stays withing the processing quota (you use the UNUSED credits of the users at the end of the month). Within a short time you could create a gigantic library. It also can become an extra incentive for new users to get an subscription.  You don\u0027t have to use all credits in the beginning, you could begin with 20% of it and see how it effects the service and increase as the months go by.

Paul_design · Answer

Hi r0n!\u000a\u000a1)Yes, one credit is one icon generation.\u000a\u000a2) No unfortunately, .ico file cannot be created in a different resolution with the Favicon tool (only 48x48).\u000a\u000a3)Thank you for the suggestion, this is a very interesting one! Our team will discuss and consider this but I can’t make any promises at this point.\u000a\u000a4) We don’t really have any ‘leftover’ credits (the AI API is pay\u002Das\u002Dyou\u002Dgo). While this idea certainly sounds nice, if we had credits left over we would allow them to roll over to next month for our users. Unfortunately, this is not feasible.\u000a\u000aHope this answers your questions, please let me know if you have more!

itrait24 · Answer

Hi Paul you might want too check the counter I created 5 icons and maxed out my 40 credits

CandyIcons

Related questions