Official Release Packages
Stable release 0.46 intended for production use is available:
- Source Tarball — .gz See README to install, or CompilingInkscape for troubleshooting help.
- Mac OS X
- OS X 10.5, Leopard — Universal .dmg (Please first upgrade X11.app to at least XQuartz v2.1.4.)
- OS X 10.4, Tiger — Universal .dmg
- OS X 10.3, Panther — PPC .dmg
- Windows — .exe installer, 7zip
Download any of the above (as well as .sig files and previous releases) at the Sourceforge Downloads page, or through your distro's update capabilities.
A Linux Autopackage of 0.45 is also available here — .package (See autopackage.org for directions).
Unofficial Packages
The Inkscape team do not currently provide official 0.46 packages for other platforms. There are, however, some unofficial packages available;
- Fedora packages of 0.46 (FC-8 or 9), or 0.45 (FC-4 to 7) can be found here. Or type:
yum install inkscape
- Suse has 0.46 packages for 11.0, or 10.3, and 0.45 packages for 10.1 and 10.2.
Please let us know about packages for other platforms or distributions, and we will add them as we receive information.
Development Versions
For those wishing to use the latest and greatest "bleeding edge" features and willing to risk more instability, or those wishing to test out the newly added code to help identify and debug problems in the code, access is provided to the development versions. Use at your own risk, and please report bugs you find!
Compiled Packages
If you don't want to compile the code yourself, use the nightly build for your system:
Windows:
Linux:
- Autopackage Builds — See Autopackage Site for directions
- ZeroInstall feed — see 0install.net for more information
- Gentoo Dependencies — make sure everything has been compiled by the same version of g++. C++ ABI changed between gcc 3.3 and 3.4
- Debian Dependencies — everything is available in the unstable apt repositories.
Mac OS X:
- Mac OS X packaged application (.dmg), named by date.
Please note that builds may not be available on days when there are compilation issues for some platforms. Rarely, a build may not run. If you notice either situation, please report ASAP so it can be investigated and fixed.
Source Code Packages
You can also obtain the source code and compile it yourself, in one of several ways:
SVN:
Tarball Snapshots:
Package Signatures
Some of the packages have been signed by the packager. Here is where to find their GPG public keys:
- Kees Cook — GPG#17063e6d
- Aaron C Spike — GPG#855781ba
- Bryce Harrington — GPG#E0E67611