Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am currently looking for a .NET component that fulfills the following requirements.

  • TIFF files
    • Extracting single pages as images
    • Writing the images to new TIFFs
  • Support for colored TIFFs/Images
  • Improving the TIFF files (deskew is a must, despeckle etc optional)
  • Royalty-free deployment on servers
  • Fully architecture independent (only one assembly for x64/x86)

I have found that Libtiff.Net is capable of handling the tiff files, but the API is still very complex and it cannot improve the files.

For improvements, I am trying out AForge.NET(, but its filters require converting the images to specific pixel formats depending on the operation.

share|improve this question

closed as not constructive by gnat, Martijn Pieters, Yannis Mar 23 '13 at 11:42

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

Have you looked at the freeimage library? I can't quickly tell whether it can edit/improve the TIFF, but it looks to be able to do the rest.

share|improve this answer
Unfortunately, it cannot do the improvements, but the API seems to be a bit easier to use than LibTiff.NET(for what I need). – Alex Feb 3 '11 at 14:11
up vote 0 down vote accepted

We are now probably going with GdPicture.NET, which has the drawback of not fulfilling the platform requirement (--> seperate assemblies for x64 & x86).

However, it was the only affordable component for some of the weird formats we are using around here (OJPEG as input, files that Windows(GDI+) can't open...).

Edit: The component now provides a fully managed core assembly, thereby eliminating the need on our side to build multiple versions of our software.

share|improve this answer
If this is the best solution you found to your problem, you should accept your own answer. – Matthieu Dec 8 '11 at 14:02

Have a look for ImageKit component.

a 100% managed .NET imaging component... With the ImageKit.NET, application programmers can quickly and easily add powerful imaging capabilities to their .NET applications.

The ImageKit.NET contains not only Windows Form controls but also Web Form controls and supports VS2008, VS2005, and VS2003.

There are numerous sample programs included illustrating common imaging tasks. Each sample shows one or two tasks, keeping the sample programs easy to understand and allowing you to use the samples to aid in building your imaging applications.

The ImageKit.NET can retrieve digital images from TWAIN scan devices and digital cameras. It can load and save image data in a variety of formats. It contains numerous effect filters and image transformation methods allowing you to resize, rotate, compose images, and do much, much more.

share|improve this answer
Why? What makes it good? What's not so good about it? Please expand your answer. – Walter Feb 1 '11 at 12:51
Some files were wrongfully deteced as single-page, whereas some could not be opened at all. I will contact support, If they can fix it, it may be a possibe solution. – Alex Feb 3 '11 at 14:29
After some contact with the support: ImageKit can not open files that Windows itself is unable to open(GDI+), which ruled it out for our project. – Alex Feb 8 '11 at 11:42

Not the answer you're looking for? Browse other questions tagged or ask your own question.