Thank you for the feedback. We will investigate what options there are for improving the quality of the saved image. Let me provide you with some more information on how the current implementation works, as well as some immediate suggestions to try.
There is a level of abstraction behind the ImageManager, allowing for developers to plug in a different image provider, such as a database. It is this provider, and not the ImageEditor itself that does the actual saving. It is also possible to subclass this provider, and implement an alternative saving method.
More information on this provider can be found in this online demo:
At present this is how the "default" ImageProvider saves the [cropped] image file:
override string StoreBitmap(Bitmap bitmap, string url, ImageFormat format)
As you see, the implementation lets the .NET framework take care of the save process. It seems that the frameowrk does not do such a good job with its default algorithm when it comes to saving .jpegs.
For the time being, what you can try is subclass the Telerik.Web.UI.Widgets.FileSystemContentProvider
class (it is public), override just this one method with a more advanced save method, and set the editor to use the subclassed provider, e.g.
We will research ourselves what alternatives exist to the default .NET jpeg saving mechanism, and we hope to soon come out with a solution that provides better results.
the Telerik team