I am somewhat new to Krita, I had it installed for some time but rarely used it, but now I want to get away from Photoshop and Adobe and like Krita much better than GIMP.
One thing I was missing were the Photoshop vector shapes. So here is a Python script that converts Photoshop csh and psp files to Krita svg shapes.
It comes as a plugin and as a standalone Python file with a TKInter UI. Tested on Windows and MacOS (should work on Linux).
Edit 20260331: Plugin was updated to also work with Krita 6.x. Please test.
Edit 20260331: Minor fix: There was an update, since the html file that is shown in the plugin manager did not work correctly in Dark Mode. Please download new version from Codeberg.
Thank you for sharing your work with the community!
Without having tested it so far, did you already adapt it to the changes introduced through the very recent update to the Qt5 based Krita 5.3.x and the Qt6 based Krita 6.0.x?
Thank you for the information!
Since Krita 5.3.0 is the current formal release, Krita 5.3.1 is awaited for the coming week, this will serve most users. But because we also have a lot of users who are already working with Krita 6.0.0, although it has some bugs that must first be ironed out, before it also gets a formal release, you will probably make those users happy about the fact that your plugin will work for them too. But the decision is up to you.
To get all the available recent and previous release versions of Krita, you have to know where to look, to be able to find them. Recent versions of Krita are found here:
And previous versions of Krita, down to version 2.4.7.5 are found here:
@Michelist Thanks for the information, I found the nightly of the Windows version a few minutes ago, after I looked again. Can I install 6.x alongside 5.x or will it overwrite my productive version?
If this is possible I will gladly update for Krita 6 (or test if it already works).
Please use the portable version, so the ZIP file without dbg in the file name, this way it will not overwrite your working version. There is one thing to obey, if you don’t want Krita to constantly rebuild the resource database, you should create a backup of the file resourcecache.sqlite before you start the other version, you will find it in Krita’s resource folder. Additionally, I would do the same for your kritarc. That way you can exchange them before changing the version. But there is another alternative without that hassle and a 100% clean split of versions, create a second user account, and if you then create a link for the version in the other user account using the runas option, you can even run them simultaneously. This way I’m doing support for the forum, there were times I ran 7 and more “Krita’s” simultaneously as you can see here. You only need a decent amount of RAM … :
Creating a different user is not possible on my main machine for various reasons and always copying the database and kritarc back and forward also is not very user-friendly. I do not know if here is the right place to suggest this or if I should take it directly to the devs, but wouldn’t it be better if the portable version would either
save the config and database in the local folder (it is not portable anyway, if Krita writes to the host machine. If I install it on a USB-stick for full portability for example, I would miss my configs if and when I start on another computer. Or am I missing something here?)
ask me on first start where to save config and database, so I would be able to run both versions alongside without much fuss.
Or did I understand something wrong about the portable version? Other portable softwares keep everything local so I actually can use them from a USB-stick or external drive.
I now have Version 6 installed on another computer and the plugin does not work with it. I will update it for Krita 6 when I find the time and report back here.
Thank you for looking into it. Those who want to use your plugin with Krita 6 will probably be happy to hear about this.
And now to your question from the second to last post:
For my knowledge the Krita devs do not plan to change this, but there are solutions. One that offers are real portable version, although it also writes into %LOCALAPPDATA% and %APPDATA%\krita\, is the version from Krita Portable | PortableApps.com. They haven’t updated to 5.3 right now, but usually that happens relatively quick. Their “trick” to offer portability without touching the Krita binaries is to mirror those files Krita writes while running into the directory tree of their kind of portable Krita. For those who don’t want to run several versions of Krita, this is a possible way to take their Krita with them, but it bears the danger to overwrite a different user’s Krita settings if plugged into a PC with a Krita installation.
Then there was a discussion in ~ the last year, I haven’t found so far, where the users involved into that discussion worked out a way to create an apparently real portable Krita not showing these issues, at least if I remember that correctly, because for a longer time now I miss a lot of things here in the forum because of health issues. These issues lead to me sometimes mixing up things that don’t belong together, and additionally I’m often days late in answering open questions, as you just experience yourself. So, when I have found that discussion, I will put a link to it in this topic.
For me that sounds to be the best way so far to create clean separated versions of Krita using portable versions.
And in the same topic Krita’s maintainer halla wrote what the Krita devs would have to change for creating such a version. But because she didn’t write that they will or want to do that, I assume that from the official side there exists no interest in doing so.
Thank you for your insights. No need to apologize if responses take some time, we all have a life.
On another note, for all reading this thread: There was an update, minor fix, since the html file that is shown in the plugin manager did not work correctly in Dark Mode.
Hello 