Frequently asked questions

From Inkscape Wiki
Jump to navigation Jump to search

deFAQ - FAQ in German - work in progress


Q: What is Inkscape?

Inkscape is an open source drawing application similar to Adobe Illustrator, Corel Draw, Freehand, or Xara X. What sets Inkscape apart is its use of Scalable Vector Graphics (SVG), an open XML-based W3C standard, as the native format.

Q: Is Inkscape ready for regular users to use?

Yes! While Inkscape does not have all the features of the market leading proprietary software, the latest versions provide for a large portion of basic vector graphics editing capabilities. People report successfully using Inkscape in a lot of very different projects (web graphics, technical diagrams, icons, creative art, logos, maps). See examples at the Galleries. We try to always keep the codebase usable for real users, as we believe that a tight iteration cycle between users and developers will give best results. You can start using Inkscape alongside your other tools now!

Q: What platforms does Inkscape run on?

We provide binary packages for Linux, Windows (fully self-contained installer), and OSX (dmg package). We know that Inkscape is successfully used on FreeBSD and other Unix-like operating systems. Windows 98/ME is no longer supported, however, maybe at a later time.

Q: How did Inkscape start?

Inkscape was started as a fork of Sodipodi, in late 2003, by four Sodipodi developers: Bryce Harrington, MenTaLguY, Nathan Hurst, and Ted Gould. Our mission was creating a fully compliant Scalable Vector Graphics (SVG) drawing tool written in C++ with a new, a more user friendly (Gnome HIG compliant) interface and an open, community-oriented development process. Within several months the project had produced several releases, demonstrating a sequence of significant new features and improvements to the codebase and quickly established Inkscape as noteworthy Open Source project.

Q: What does 'Inkscape' mean?

The name is made up of the two English words 'ink' and 'scape'. Ink is a common substance for drawings, and is used when the sketched work is ready to be permanently committed to paper, and thus evokes the idea that Inkscape is a ready for production work. A scape is a view of a large number of objects, such as an landscape or ocean-scape, and thus alludes to the object-oriented nature of vector imagery.

Q: Can I create webpages with it?

Not yet, although many users use Inkscape for webpage mockups or generating web imagery such as banners, logos, icons, and more.

With the recent advances in SVG support in web browsers (such as Firefox or Opera), using SVG directly on the web becomes more of a possibility. SVG and XHTML can in theory can be used together within the same document, so interested users or developers can explore this possibility further.

Q: Can I create animations with it?

No, Inkscape does not support SVG animation yet. It is for static 2-D graphics. However you can export graphics from Inkscape to use it in Flash or GIF animations. And since Feb-2006, Blender can import SVG data and extrude it to render 3D graphics.

Q: Will there be an Inkscape 1.00? What would it be like?

Assuming development continues steadily, we will inevitably hit 1.00, but no particular development event has been planned to coincide this release, although it will likely include a few congratulatory beers. In advance of going gold with any kind of 1.00 release there would be a significant effort to tie down loose ends, a push for greater stability and smoothing off of rough edges.

This would be a time consuming process and until it does happen Inkscape may be subject substantial changes between release.

Contributing to Inkscape

Q: How can I help?

Grab the code and start hacking on whatever draws your attention. Send in a patch when you're happy with it and ready to share your efforts with others. We also need writers and translators for the user manual and interface internationalization (I18N) files.

We take contributions very seriously and follow the principle of "patch first, discuss later", so it is highly likely your efforts will appear in the development codebase swiftly. There are of course rules and standards that must be followed, but we try to keep them unsurprising and obvious.

Q: Are there non-coding ways to help?

Certainly! While there is certainly a lot of coding work to be done, there are also a lot of other non-programming tasks needed to make the project successful:

Bug wrangling and testing:

Identifying and characterizing bugs can help a HUGE amount by reducing the amount of development time required to fix them.

  • Find and report bugs. This is critical need for ensuring the quality of the code.
  • Review and verify reported bugs. Sometimes the bug reports don't have enough info, or are hard to reproduce. Try seeing if the bug occurs for you too, and add details to the description.
  • Performance Testing - Create SVG's that stress out Inkscape, and post them as test cases to the Inkscape bug tracker, with your time measurements.
  • Compatibility Testing. Compare the rendering of SVG's in Inkscape with other apps like Batik and Cairo, and report differences found (to both projects).
  • Bug prioritization. Bugs that are marked priority '5' are new bugs. Review them and set them to high/medium/low priority according to their severity. See Updating Tracker Items in wiki for details.

Helping fellow users

In addition to making a good drawing app, it's also extremely important to us to build a good community around it; you can help us achieve this goal directly, by helping other users. Above all, keep in mind that we want to maintain Inkscape's community as a nice, polite place so encourage good behavior through your own interactions with others in the group.

  • Write tutorials. If something isn't already documented in a tutorial, write up a description of how to use it.

  • Participate on inkscape-user@. Answer questions that pop up on the mailing list from other users. Also, share your tips and tricks, and demo new ways of using Inkscape for cool stuff.
  • Create clipart. You can upload it to the project.
  • Give Inkscape classes. Teach people local to you about using Inkscape. Or give presentations at local events, Linux group meetings, etc. about Inkscape (and other Open Source art tools.)

Development (no coding needed)

  • Translations. Information on how to create translations for the interface is available on the TranslationInformation page in Wiki.
  • Design Icons and SVG themes. Create new icons for existing themes or start a new icon theme. Also see
  • Mockup new dialogs. Draw up ideas for improving or adding dialogs. These are handy to the UI developers for figuring out what to do.
  • Improve packaging. Figure out how to make the package for your operating system or Linux distribution install and work better. See CreatingDists in Wiki.
  • Add extensions. For file input/output, special features, etc. Inkscape is able to tie into external programs. Create new .inx files to hook these up for use in Inkscape. Also, if you're comfortable scripting in Perl, Python, etc. have a shot at improving the extensions, too!
  • Create templates. See the Inkscape share/templates directory.
  • Work in Wiki. Wiki is a great place for gathering development info but always needs updating, copyediting, and elaboration.
  • Plan future development. Review and help update the Roadmap in Wiki. Basically, talk with developers about what they're working on, planning to work on, or recently finished, and update the roadmap accordingly.

Spread the word - Inkscape Marketing and Evangelism

Increasing the size of the userbase is important. The network effects of more interested users means more potential contributors and hopefully people saying nice things about us, and giving Inkscape word of mouth advertising which we believe is important. All our users and developers serve as ambassadors for Inkscape and others will judge Inkscape based on how well you behave. It is important that we all be polite and friendly and make Inkscape a project people like using and enjoy working on, all other evangelism follows on naturally from there. Generally though for building the community we prefer quality over quantity so be careful to not go too overboard with evangelizing or the "hard sell". We want to work with other applications, rather than "killing" off other software and such comments are counter productive. We need to manage expectations. We want users to be pleasantly surprised by how much Inkscape does, not disappointed that it does not match other programs feature for feature. Inkscape should be thought of as providing artists another way to be creative which compliments their existing skills and tools.

  • Write Articles. Get articles published in various online (or even printed) magazines and blogs. Don't forget to include a link to Inkscape!
  • Create Screenshots. Especially for new features.
  • Create Examples. Examples are useful for showcasing different ways Inkscape can be used. Create some screenshots and text, and submit to the web wranglers (via the inkscape-devel mailing list) to add to the site.
  • Work on the Website. Help on the website is ALWAYS appreciated. Knowledge of HTML is required; PHP know-how is helpful. Check out the website code from CVS and send patches, or request direct CVS and shell access for doing on-going work.
  • Give presentations. Give talks at expos, symposia, and other big events about Inkscape. Be sure to announce it on a inkscape mailing list so we can post it to the Inkscape website.
  • Recruit more developers. Find people with an interest in doing coding, and encourage them to work on Inkscape.

Q: Where can I get a banner for Inkscape?

Here's one:

Feel free to contribute your own banners or buttons for promoting Inkscape. The best ones will be linked here.

Development topics

Q: What are Inkscape's Development Goals?

Inkscape seeks to implement a complete SVG-compliant vector graphics editor. Uses of such an editor include a broad range - logos, vector artwork, technical diagraming, map making, and more.

Q: What language and toolkit is Inkscape built upon?

The codebase Inkscape inherited from Sodipodi was C/Gtk based. There is an ongoing effort to convert the codebase to C++/Gtkmm. The ultimate goal is to simplify the code and make it more maintainable. We invite you to join us. Just don't mention Qt. :)

Q: What is your position on code sharing with other projects?

Yes, sharing of code libraries with other projects is highly desireable, provided the right conditions exist. A good candidate for a library will be mature, widely distributed, well documented, and actively maintained. It should not introduce massive dependency problems for end-users and should be stable, powerful, and lightweight. It should strive to do one thing, and do it well. Libraries that don't meet all the criteria will be considered on a case-by-case basis.

Q: What's a good way to get familiar with the code?

In the Documentation section of the website you can find some high level diagrams, and links to other documentation that's been produced such as the man page. Historically, this codebase has not been kept well documented so expect to find many areas where the only recourse is to work through the code itself. However, we place importance on working to change this, and to flesh out the documentation further as we go.

Some developers have found that testing patches is a good way to quickly get exposure to the code, as you see how other developers have approached making changes to the codebase. Other developers like to pick an interesting feature request (or perhaps a feature wish of their own) and focus on figuring out how to implement it. Occasionally we also have large scale grunt-work type changes that need to be applied to the codebase, and these can be easy ways to provide significant contributions with very little experience.

Getting beyond initial exposure, to the next stage of understanding of the codebase, is challenging due to the lack of documentation, however with some determination it can be done. Some developers find that fixing a crash bug by tracing execution through the various subsystems, brings good insights into program flow. Sometimes it is educational to start from an interesting dialog box and tracing function calls in the code. Or perhaps to start with the SVG file loader and follow the flow into and through the parser. Other developers have found that writing inline comments into the code files to be highly useful in gaining understanding of a particular area, with the fringe benefit of making that bit of code easy for future developers to pick up, too.

Once you feel far enough up the learning curve, implementing features will firm up your experience and understanding of the codebase. Be certain to also write test cases and documentation, as this will be of great help to future developers and thus ensure the longevity of the codebase.

Q: What is the size and composition of the codebase?

The latest statistics are available at The code is somewhat modular, but less so than we would like it too. If you're interested in some specific part of the codebase, feel free to ask developers.

Q: What rendering engine do you use?

Currently we use our own renderer called livarot. We plan to migrate to Cairo when it is mature enough.

Q: What is the development platform?

Most developers work on Linux. However it is also possible to compile Inkscape on Windows; this page provides detailed instructions for this as well as for cross-compiling Windows binaries on Linux.

Q: What is the Linux command to download the code through CVS?

Directions are under the CVS link on the inkscape sourceforge page.

cvs login
cvs -z3 co inkscape

where you'd replace 'modulename' with 'inkscape'. Other modulenames you can check out include: 'experimental', our development "scratchpad" for working up prototypes; 'inkscape_web', which holds our website files; and 'inkscape_project', which holds config files and other project-level things.

Q: How are feature requests selected for implementing?

Many developers become involved because they wish to "scratch an itch", so of course if they wish to work on a particular feature, then by definition that one will receive implementational attention. This is the primary mechanism by which features get implemented.

Inkscape also strives to take user requests for features seriously, especially if they're easy to do or mesh with what one of the existing developers already wants to do, or if the user has helped the project in other ways.

If you have a feature that you'd really like to see implemented, but others aren't working on, the right thing to do is delve into the code and develop it yourself. We put great importance on keeping the development process open and straightforward with exactly this in mind.

Q: I'd prefer the interface to look like ...

Understandably, many users are accustomed to other programs (such as Illustrator, the GIMP, etc.) and would prefer Inkscape to follow them in design. Inkscape developers are constantly examining other projects and on the look for better interface ideas. A large motivation is to make the application follow the GNOME Human Interface Guidelines, which has a number of rules in how the interface is made. The Inkscape developers also seek advice and ideas from other GUI app designers, such as the GIMP crew, AbiWord, and Gnumeric; they've been at it longer and we view them as an excellent source of battle tested experience.

But please understand that the Inkscape interface will, at the end of the day, be the "Inkscape interface". We will strive to find our own balance of compatibility with common drawing programs, wishes of our userbase, good workflow, creativity of our developers, and compliance with specs. It's unlikely that this balance will meet every user's wish, or achieve 100% compliance with the various platform specific Interface Guidelines, or include every developer's idea, and if it did it probably wouldn't be as good.  ;-)

Usually when we discuss interface look and feel needs, we arrive at the conclusion that really, it should be configurable so that each user can flip a few switches and gain an app that is most cozy to them but flexibility should not be used as an excuse not to make tough decisions. Hopefully we can evolve in that direction.

SVG topics

What SVG features does Inkscape implement?

The main parts of SVG that Inkscape does not support yet are filters, animation, and SVG fonts. The rest mostly works, though of course there are bugs that we're always fixing. For a comparison of Inkscape and other open source SVG tools on the W3C SVG test suite, look here.

Q: What is 'Scalable Vector Graphics'?

Scalable Vector Graphics (SVG) is a type of file format for graphics that allow you to define shapes using vectors to specify points, radii, rotations, and so forth. This means that after you've drawn your image, you can easily edit any of the shapes, very easily. A rasterization engine uses this information to determine how to plot each line and curve.

Another common kind of graphic is a "raster bitmap". Bitmaps are just arrays of pixels of different colors. Once you've drawn something in a bitmap, you cannot scale or edit the shapes quite so easily. If you stretch or shrink the image, the quality of the picture is diminished because the pixels get re-interpolated (usually introducing lots of errors).

Vector graphics do not have these problems because they are represented as distinct drawing elements - ellipses, boxes, lines, and text. Because they are described this way, the plotter is able to re-render the graphic to fit any level of resolution.

Vector graphics are not an alternative to raster graphics, though, because each has its own purpose and are useful for different kinds of things. Raster graphics tend to be better for photographs and for situations where a vector graphic rendering engine is impractical or would be too slow.

Q: What is "Inkscape SVG" as opposed to "Plain SVG" when saving a document?

Inkscape SVG files use the Inkscape namespace to store some extra information used by the program. Most other SVG programs will not understand these extensions, but this is OK because the extensions only affect how the document is edited, not how it looks. Extensions should not cause any rendering problems in SVG-compliant renderers. However, some (not fully compliant) programs may have trouble with the presence of the extensions, thus the "Plain SVG" option is provided to save the file with no extensions.

Q: I have hand-created SVG. Will everything be messed up, if I load and save it with Inkscape?

Inkscape strives to avoid changing the SVG just because it does not recognize some of the SVG elements, however it *does* make changes:

  • All objects will get unique "id" attributes. If already existing and unique, they will be preserved, otherwise one will be derived from node name.
  • Some sodipodi: and inkscape: namespaced metadata will be added to the beginning of document.
  • If you edit a gradient, that gradient will be broken up into 2 linked gradients - one defining color vector, another one position.
  • Changing any style property forces reconstructing of the whole 'style' attribute, which means CSS (not XML) comments will be lost and formatting of CSS may change.
  • The formatting style of the SVG file will be changed to follow the style hardcoded into Inkscape.

There is ongoing work to allow Inkscape to better preserve hand-created SVG markup but it is a very difficult task requiring a lot of infrastructure work and will happen very gradually - but help is always appreciated.

Q: Inkscape and renderer X show my SVGs differently. What to do?

That depends on X. We accept Batik and Adobe SVG plugin as authoritative SVG renderers because they are backed by some of the the authors of the SVG standard and really care about compliance. This may not be true for other renderers. So if you are having a problem with some renderer, please try the same file with either Batik or Adobe, or better yet, with both (they are free and cross-platform). If you still see a discrepancy with Inkscape rendering, we want to look into it. Please submit a bug; don't forget to attach a sample of the problem file to the bug report, and ideally include screenshots too.

Using Inkscape

Q: Can Inkscape be used from the command line?

Yes, indeed it can. For details refer to the manual page via man inkscape after you've installed it, or view the <a href="">man page</a> on our site.

Q: I'm having problems with non-Latin filenames on Linux - help!

If your locale charset is not UTF-8, then you need to have this environment variable set:


This is necessary for Glib filename conversion from the locale charset to UTF-8 (used in SVG) and back to work. See <a href="">this page</a> for more details.

Q: How to insert math symbols or other special symbols in the drawing?

When editing text on canvas, press Ctrl+U, then type the Unicode code point of the symbol you need. A preview of the symbol is shown in the statusbar. When done, press Enter. A list of Unicode codes can be found at; for example, the integral sign character is "222b". You must have a font installed on your system that has this character; otherwise what you'll see is a rectangular placeholder.

When editing text on the Text tab of the Text and Font dialog, you can use any GTK input modes that your GTK installation supports. Consult GTK documentation for details.

When saving your work in eps format, we recommend to set the option "convert text to path" in the export dialog box, to preserve the symbol.

Q: How can sine curves be made in Inkscape?

In 0.43, Inkscape includes an extension called Function Plotter (before that it was called Wavy). It can be used to create sine curves or any other function graphs. Third party software such as Xfig, KiG, or KSEG can also be used to create complex mathematical curves and then export to SVG for use in Inkscape.

Q: Does Inkscape support palettes? Where can I "store" and save colours for further use?

Starting from 0.42, palettes are supported using the same file format as the GNU Image Manipulation Program (GIMP Colour Palettes, .gpl). The name used in Inkscape for the feature is "swatches". When selecting this terminology, we surveyed a number of different programs and found that both "palettes" and "swatches" were commonly found. Since the term palettes had been already been used in Inkscape to describe a particular type of dialog windows, the latter term "swatches" was adopted to describe this feature.

Q: How do I get extensions working?

The extensions mechanism allows you to use external programs and scripts written in any language to augment Inkscape's capabilities. The tricky part is satisfying all of the dependencies of the external programs. For help satisfying dependencies of individual extensions check GettingExtensionsWorking. If you are specifically interested in Effects go straight to GettingEffectsWorking; if you're on Windows, consult GettingEffectsWorking/Windows. {WHAT ABOUT OSX?}

Q: How can I print the tutorials? When printed from Inkscape they don't fit, and I don't like reading on screen.

All tutorials in all languages are available online in HTML at and can be easily printed from your browser.

Q: Is there any way to specify a stroke that has a gradient applied along its length?

A stroke can be painted with a gradient, but that gradient will not bend with the stroke. It will remain linear or elliptic. If you meant something like this then no, inkscape can't and to my knowledge SVG can't (easily) either.

Q: I am working on a machine with operating system xxx which has default language yyy set, but I want to work with Inkscape menus in language zzz (most likely English), how can I set this?

LANG=C inkscape in the commandline switches to the default language (English).
LANG=fr inkscape changes the language to french. This command is only used by the started program. The
used locale has to be installed (else it falls back to the default language). To change it easier in the future, you can use an
alias alias inkscape="LANG=C inkscape"
You have to save that in the .bashrc , so that you can use it even after the next system restart. Type locale -a in the console
to find out, which locale setting is supported on your system.

The official Mac OS X way is to provide .lproj files which enables applications to pick up the
preferred language
from the System Preferences dialog; however, this is probably some considerable
way into the future. It might be possible to set up a scheme involving langauge :: packs, otherwise the linux methods may work.
1. Locate the installation directory.
2. Enter the Inkscape\locale directory
3. Locate the directory with the two letter locale you don't want to use.
4. Rename (or remove) this directory to something like disable_de or x_es
5. Restart inkscape and the default English (en) locale will be used.
Beware, this change the behaviour for all inkscape users on this machine

Q: I'm trying to make a colored tiling of clones, but the tiles refuse to change color.

The original object from which you're cloning must have its fill unset for this to work. Use the "?" button in the Fill&stroke dialog to unset fill. If the original is a group, only some of the objects in the group may have unset fill, so only these objects will change colors in the tiling.

Q: The PNGs exported by Inkscape have jagged edges/no antialiasing/funny background.

This is a problem with whatever you use to view these PNG files, not with Inkscape. For example, Internet Explorer cannot show PNG files with transparency properly. Use e.g. Firefox to view your PNGs. If you absolutely must use IE, you can't have transparent background in PNG; change it to opaque in Document Preferences and export the PNG file again.

If you want to open the exported PNG bitmaps in MS-Word, you will also have to change the alpha-opacity (in document-properties dialog) to full, and then export -- the result will be much better.

Q: I installed a new font on my Windows system, but Inkscape does not see it.

This is a bug caused by Inkscape using an obsolete font cache. This cache is stored in the file called .fonts.cache-1. This file may be in your Windows folder, or in your Temp folder, or in "My documents" folder, or in the folder listed in the $HOME environment variable. Use file search by name to locate this file. Then simply delete this file and restart Inkscape; now it will see the new fonts.

Inkscape and other programs

Q: Why the split from Sodipodi?

Inkscape started as a code fork of Sodipodi. The main reasons were differences in objectives and in development approach. Inkscape's objective is to be a fully compliant SVG editor, whereas for Sodipodi SVG is more a means-to-an-end of being a vector illustration tool. Inkscape's development approach emphasizes open developer access to the codebase, as well as using and contributing back to 3rd party libraries and standards such as HIG, CSS, etc. in preference to custom solutions. Reusing existing shared solutions helps developer to focus on the core work of Inkscape.

For background, it may also be worth reviewing Lauris' [ Sodipodi direction] post from Oct 2003, and his thoughts on SVG, licensing, and the value of splitting the project into two independent branches.

Q: What's the difference between Inkscape and Dia?

Dia is for technical diagrams like database charts, class diagrams, etc., whereas Inkscape is for vector drawing such as logos, posters, scalable icons, etc.

SVG is a useful format for creating diagrams, though, so we hope as Inkscape grows as a fully-featured SVG editor, it will also be useful for making attractive diagrams too. Several of us hope Inkscape will become a useful technical drawing tool and work on features with that goal in mind. However, Dia provides a number of useful capabilities such as support for UML, autogeneration of diagrams, etc. that are well beyond the scope of a general SVG editor. Ideally both Inkscape and Dia can share various bits of code infrastructure and third party libraries.

Q: Is this intended to replace Flash?

No, while SVG is often identified as a "Flash replacement", SVG has a huge range of other uses outside that of vector animation. Replacing Flash is not one of Inkscape's primary intents. If SVG can replace Flash, and Inkscape can help, that's great, but there's a lot more to SVG than web animation that is worth exploring. (See also SMIL

Q: Is Inkscape a replacement for The GIMP?

Certainly not! No more than a microwave oven is a replacement for a toaster oven, or a hammer a replacement for a chisel. Inkscape and The GIMP are both graphics tools, but they're used for two very different things. Inkscape is used for creating vector drawings, such as laying out a poster or creating a fancy logo, whereas The GIMP is used for working on raster images, such as cleaning up a photograph or editing a GIF file.

Just as you'd probably use BOTH a microwave AND a toaster to cook lunch, or a hammer AND a chisel to carve stone, you'd probably want to use both Inkscape and The GIMP for certain artistic tasks.

Q: Will Inkscape be part of the Gnome-Office?

Inkscape will need to mature a bit further before this can be considered. Specifically, better support for embedding (Bonobo) is needed, and the Gnome-Print subsystem needs to be tested more thoroughly (help very much appreciated here). If you can compile a recent version of Inkscape and help us with testing it would be very useful.

Q: What formats can Inkscape import/export?

Inkscape natively supports only SVG, SVGZ.

Depending on your setup you may also be able to open Adobe Illustrator (*.ai), and Dia (*.dia) files.

Inkscape can save as SVG, SVGZ, PDF, Postscript (*.ps), Encapsulated Postscript (*.eps), Encapsulated Postscript Interchange (*.epsi), Adobe Illustrator (*.ai), LaTeX (*.tex), and POVRay (*.pov).

Inkscape can import most raster formats (JPG, PNG, GIF, etc.) as bitmap images.

See FileTypes for discussion about file formats that people would like to see supported, and third-party tools that can be used to convert files to or from SVG.

Q: What can I do with *.cdr (Corel Draw Vector drawing file) files in Inkscape? I have got my images in *.cdr files and I would like to continue in *.SVG.