Third (and hopefully last) release candidate for Greenshot 1.2

Okay – finishing line in sight :) we have uploaded the third release candidate for Greenshot 1.2. We have been working on ironing out a few more bugs of the latest version, as well as a few improvements and some user interface fine tuning. Again, thanks to anyone who supported us with their valuable feedback. You are doing a great job, we really appreciate that.

Most notable improvements are: torn edge and drop shadow settings are now stored and remembered next time, we have also improved the usability of the torn edge settings dialog. In the editor, the font family selection now displays its entries using the respective font so that it is easier to find the font you are looking for.
We also got rid of several bugs, mostly related to the editor, e.g. the new speech bubble feature still had some flaws.

See below for the complete changelog of the third release candidate, if you haven’t seen the previous ones yet you might want to have a look at the changelog of RC1 and RC2, too. In any case, you should check out the new release candidate – as always, it can be downloaded from our version history (

Yeah, you know that already, but just to be sure: “release candidate” means that this version has not gone through extensive testing yet. It might be buggy, so if you do not like surprises, we suggest to stick with version 1.1 until we have ironed out all issues and publish the stable release of version 1.2. In case you encounter any problems with the release candidate, please file a bug report – thanks a lot.

* Greenshot now stores the settings of the torn edge & drop shadow effects
* FEATURE-776: Improvement of the torn edge settings dialog
* FEATURE-777: Improvement of the tool settings (font family)

* Optimized Greenshots update check to use even less traffic by checking the time-stamp of the update feed before downloading it.

Bugs Resolved:
* BUG-1620: Greenshot crashing Chrome running in 'Windows 8 Mode'
* BUG-1682: Speech bubble tail "gripper" moved outside of the drawing area, making it impossible to move the tail
* BUG-1686: Shadow (drop shadow or torn edge) grows if a filter (highlight etc) is used and an element is moved around
* BUG-1687: Speech bubble didn't have a working shadow
* BUG-1698: Cannot enter textbox/Speechbubble lowercase text after changing font family
* BUG-1699: UI jumps when Textbox or SpeechBubble tools are selected, and changing to another tool. (also the other way around)
* BUG-1700: IE capture only works once
* BUG-1701: Drop shadow setting "shadow thickness" wasn't restored.
* BUG-1709: Alignment of the text and speech-bubble wasn't always correctly saved in the .greenshot file
* BUG-1710: After resizing the canvas the edges had a slightly different color (1px)
* BUG-1711: Changing settings (e.g. fill color) on the speech bubble before drawing it, caused an exception.
... and a lot more small changes to make Greenshot more stable.

Posted in Releases | Tagged , | Leave a comment

Second release candidate for Greenshot 1.2

It’s time for another release candidate for Greenshot 1.2. If you have tried the first release candidate, you probably already saw some of the brand new features like the speech bubble tool in the editor. Thanks to the awesome users who came up with useful bug reports and suggestions we now have ironed out some things that were not working perfectly yet.

But that’s not all: a few small features have made it into the new release candidate also.

  • There’s a new option to resize the icons (e.g. of the editor toolbar), so they will be recognizable again if you are using a high-resolution display. (Most of the icons used are still optimized to be displayed at a size of 16 x 16 pixels, so they might look a little bit blurred when enlarged. We will add new (vector) icons when the time has come for an editor redesign.)
  • The last capture region can now be re-used even after a restart of Greenshot or a reboot.
  • In region mode, the area to capture can now be selected using the keyboard: use arrow keys to move the cursor, then Enter to lock one corner of the region and – after moving the cursors on – hit Enter again at the opposite corner to capture the region

See below for the complete changelog of the second release candidate, if you haven’t seen the first one yet you might want to have a look at the changelog of RC1, too. In any case, you should check out the new release candidate – as always, it can be downloaded from our version history (

And, as usual, the disclaimer: “release candidate” means that this version has not gone through extensive testing yet. It might be buggy, so if you do not like surprises, we suggest to stick with version 1.1 until we have ironed out all issues and publish the stable release of version 1.2. In case you encounter any problems with the release candidate, please file a bug report – thanks a lot.

* Added the possibility to select the region to capture by using the keyboard, use the cursor keys to move the cursor (ctrl-key speeds up the movement) and the enter key to mark the start and ending.
* FEATURE-757: Greenshot will now store the last used region in the greenshot.ini, which makes it also available after a restart.
* FEATURE-758: Due to the fact that more and more high DPI displays are used, we added a setting to change the icon size.
* Added support for another clipboard format "Format17" (aka CF_DIBV5) which should improve the result of the "open image from clipboard" and drag&drop actions.

* JIRA: With JIRA 6.x using the SOAP (Webservice) API the access has gotten really slow, we improved the performance slightly by loading some information parallel. (In Greenshot 2.x we will move to another API.)

Bugs Resolved:
* BUG-1667: removed horizontal alignment of textbox in input mode, as it caused problems with textbox focus and could not be implemented consistently anyway (no vertical alignment possible)
* BUG-1681: Improvements for the new speech bubble, text color is now the same as the border and the rounded corners are correctly calculated when using thick lines and a small bubble.
* BUG-1695: Fixed an issue with processing the response from Imgur, which caused the error "Value cannot be null. Parameter name: key"

Posted in Releases | Tagged , | Leave a comment

Release candidate for Greenshot 1.2 available

We have just uploaded the first release candidate for Greenshot 1.2. It fixes some bugs of the prior version, but, far more important, adds some features that have been requested very often… most notably, the Greenshot 1.2 editor will finally draw speech bubbles / callouts, auto-incrementing labels and offer the possibility to resize the screenshot.

As usual, the disclaimer: “release candidate” means that this version has not gone through extensive testing yet. It might be buggy, so if you do not like surprises, we suggest to stick with version 1.1 until we have ironed out all issues and publish the stable release of version 1.2. In case you encounter any problems with the release candidate, please file a bug report – thanks a lot.

And, as usal, here is the complete change log – you can download the release candidate (version – installer, ZIP or PortableApps version) from our version history:

All details to our tickets can be found here:

* FEATURE-184, FEATURE-282, FEATURE-486: Image editor now has a speech bubble
* FEATURE-281, FEATURE-669, FEATURE-707, FEATURE-734: Image editor now has auto incrementing labels
* Editor: a resize effect with settings window has been added.
* Editor: a settings window for the torn-edge effect has been added.
* Editor: a settings window for the drop shadow effect has been added.
* OneNote: Enabled and enhanced the OneNote destination, so we can test this and see if it's worth releasing.
* External command: If a command outputs an URI this will be captured and placed on the clipboard, the behavior currently can only be modified in the greenshot.ini

Bugs resolved:
* BUG-1559, BUG-1643: Repeating hotkeys are now prevented.
* BUG-1610: Image editor: 'Obfuscate' and 'Highlight' and more, now should rotate / resize correctly.
* BUG-1619: Image editor: Autocrop now also considers the elements.
* BUG-1653: Accessibility issues: Editor "File" menu entry can't be activated and missing translations

* Dynamic destination context-menu: If a destination has child items the parent is still selectable and executes the default export, we now no longer repeat the parent in the children.
* Dynamic destination context-menu: We are now leaving the sorting to the destination code, this allows us to e.g. show the default printer on top of the list.

* Updates for Ukrainian and Japanese translation

Posted in Releases | Tagged , | Leave a comment

Greenshot Switches to JIRA for Bug Reports and Feature Requests

The difference between good and great software often originates from the developers closely listening to the users. As your ideas and comments are valuable input for us, we think that you need be able to easily report bugs and request features, as well as to quickly find information on problems/suggestions that have already been reported by other users.

For a long time, we have used the Sourceforge ticketing system for this, and although it worked for us many years we always thought it wasn’t perfect for our needs. As every member of the Greenshot team also has experience with another ticketing tool, which we all like a lot, it is now time for a change.

We are proud to say we migrated the Greenshot bug/feature tracker to Atlassian Jira, a professional ticketing system. We really think that this improves overall user experience both for us and for you, no matter if you want to report an issue or simply get an overview about what we are up to for the next version of Greenshot. On top of this it is integrated with Atlassian’s BitBucket, where our source code are hosted, which makes it easy to spot what exactly has been changed and why.

Thankfully, Atlassian has a great program to support open source teams with free software services and hosting. We were already using BitBucket and now we introduce Jira, maybe other products follow.

What does this mean for you?

Well, as we hate losing information, we migrated all the current bug reports and feature requests, with the complete history, to our new system. Also all Sourceforge users who reported tickets have been copied to our Jira. The users were created having the same username as with Sourceforge but without a password. At the first login you are asked to reset your password, to make this possible you will receive an email at your Sourceforge account with instructions. After successfully setting your password and being logged in you can change your email address if you like.

Additionally we have been looking for a solution to make it easier and quicker to bring a new version of Greenshot to you, independent of whether we want to build a release or just a version which should solve the bug(s) or add the feature request(s) you reported. For .NET applications this is not easy and as Greenshot is free it shouldn’t cost money, so up to now we have been building Greenshot manually, which was very time intensive and sometimes caused a bit of stress when we forgot something and needed to start all over. Now we finally found an extremely good solution (which is also free for open source projects), and are proud to introduce AppVeyor, a Continuous Integration system for .NET applications, which builds Greenshot for us. The people at AppVeyor really created a great system, it took only a couple of hours to make our build work, and the few questions we had were answered quickly. Although you won’t notice this directly, it does make it possible for us to concentrate on the development so we hope we can fix and extend Greenshot at a quicker pace.

We hope to see you on our new Ticketing system and are looking forward to having a good time while further improving Greenshot together with you.

Posted in Announcements | Tagged , , , | Leave a comment

Greenshot 1.1.9 Bugfix Release

A new version of Greenshot is available for download, containing bug fixes and small improvements. Most notably, we have

  • fixed capture problems that came with a recent update for Windows 8.1, affecting users with multiple displays and different scaling
  • repaired upload to Box, which was broken in the previous version
  • updated Flickr plugin to be prepared for a breaking change in the Flickr API effective as of June, 27th

Please see the change log below for more details about what’s new. As always, you should make sure to download Greenshot from our download page, rather than being confident in 3rd party download portals to deliver the original version.

CHANGE LOG: Windows 8.1 & Box bug-fix Release

Bugs resolved:
* Bug #1604,#1631,#1634: Capture problems since update to Windows 8.1 with multiple displays
* Bug #1627: Box upload failed since 1.1.8
* Unreported: The greenshot.ini values "NoGDICaptureForProduct" and "NoDWMCaptureForProduct" had incorrect defaults, which might cause issues with some applications when using the auto capture mode.

* Feature #697: Added the possibility to replace characters/strings when a pattern is used, to have more control over the resulting filename. E.G. ${title:r ,_} will cause all the spaces to be replaced by underscores.
* Feature #712: The amount of colour which images are reduce to, if the setting is active, has been made configurable in the greenshot.ini property OutputFileReduceColorsTo. Default stays at 256,
* Feature #723: Adding a newline when exporting to Word or an open Outlook email, this makes it possible to repeat exports.

* Flickr plug-in: from June 27th, 2014 Flickr will only accept uploads via HTTPS! As the switch is already possible Greenshot has been changed accordingly.

* Updated the French translation for the Microsoft Office plug-in

Posted in Releases | Tagged , | Leave a comment

Happy Birthday to Greenshot + New Bugfix Release 1.1.8

Hey, did you know that Greenshot just had it’s seventh anniversary? To celebrate it, we have just uploaded a new release of Greenshot, version 1.1.8. Join the party :)

It mainly consists of bugfixes and small improvements, most notably improved clipboard support, configurable file naming for the Imgur plugin, as well as better readability when editing white or very bright text in the image editor.

As always, you can download the latest stable version from our download page.

For more details, the complete list of changes in Greenshot 1.1.8: Bugfix Release

Bugs resolved:
* Bug #1578: Changed the behavior of creating filenames for Imgur to be configurable, default will be the date/time.
* Bug #1580: removed device names for capture fullscreen submenu in multi-monitor setups, which sometimes delivered inconsistent results or even garbage characters. Sticking to descriptive text like "bottom left", which is more useful anyway.
* Bug #1581: Ini-file reading is now done without locking the file, this should help a bit in cases where other applications have this file open.
* Bug #1600: Found that Greenshot uses a wrong URL format on the clipboard, this fix might solve some issues
* Bug: When capturing client windows on a DWM enabled system (Vista & Windows 7) with "auto" set, sometimes the capture had a blurred/transparent effect.

* Feature #663: dark background for textbox input when editing bright-colored text
* Feature #667: destinations with subdestinations can now be clicked to invoke the "main" subdestination

* Updates for Swedish translation and help, new Swedish translations for plugins and installer
* Improvements for German translation and help
* Bug #1608: Fixed typo in French translation

Posted in Releases | Tagged , | Leave a comment

New Bugfix Release with Important Change for Users

So here is another release in 2013 – probably the last one ;-) Important especially for those using Greenshot’s Box plugin to send screenshots directly to is applying a breaking change to the authentication API on December 13th, which means that the Box plugin released with Greenshot 1.1.6 will no longer work – we have changed the plugin to work with the new API as of Greenshot 1.1.7.

There are also some bug fixes, especially we got rid of an annoying problem with screenshots being exported to the wrong Word document.
You can read detailed information in the change log below or download Greenshot 1.1.7 right now.

We switched our version control system from Subversion (SVN) to Git and have moved our repository to BitBucket, you can find it here:
This change makes it easier for other developers to supply patches to our code by sending us pull requests. Bugfix Release

* We moved our repository to BitBucket (GIT), this forced us to change the build script and the version

Bugs resolved (for bug details go to and search on the ID):
* Bug #1517: (now it is really fixed) export to Microsoft Word always goes to the last active Word instance.
* Bug #1589/#1584 System.NullReferenceException
* Bug #1574: AccessException when loading plugins

* Changed the Box plug-in to use the new V2 API, which is mandatory from 13.12.2013. The Box plug-in now needs the .NET 3.5 Full Framework.

Posted in Releases | Tagged , , | Leave a comment

Promised: No Bundled Installers, No Toolbars, No Unfair Advertisements

As Greenshot is a free and open source project, we depend on donations and advertising to keep the project running. You probably know that already, since we published a blog post about our thoughts of advertising not so long ago.

Recently, some users told us that bundled stuff like browser toolbars etc. had been installed on their computer by what they assumed was the Greenshot installer, which would have surprised us a lot, since there are no bundled installers or similar annoyances in Greenshot. We are convinced that bundled installers are abusing the user’s trust and therefore we strongly oppose to it, no matter how much money marketing companies pay for them. In dialog with our users and with some research we then found out that these issues actually had nothing to do with our installer at all.

Unfortunate advertisements on SourceForge and our website

The problem was of another nature: our advertising service (which happens to be the same as SourceForge’s) recently started to deliver advertisements with big green buttons on it, labeled “Download”. The advertised pages do not offer the original Greenshot installer, but other software. However, this fact is not obvious on these pages (probably intended), one of them even offered an executable called Greenshot_Setup.exe.

greenshot-2013-11-16 10_13_28Of course, we get more ad revenue when advertisements are clicked, but we certainly do not want to trick our users into clicking them accidentally, let alone into installing any other tools than Greenshot.

If this has happened to you: please take our honest apologies, we are very sorry for that. Our advertisements are delivered by Google Adsense, so if you installed anything from their ads, you might want to know that they at least have very strict rules for advertisers.

We are absolutely positive about web advertising to keep web projects going, but we believe ads must be fair and must not impose constraints on visitors.
As a consequence, we have blocked all known advertisers with those unloved “download button ads” from our website and made advertisements even more recognizable by applying a prominent border. We have also gotten in touch with SourceForge asking them to get rid of these ads, too.

Help us to keep advertisements clean

We can blacklist advertisements we regard unfair or misleading, but of course new advertisements may come in now and then. Also, depending on where you live you might see ads that we will never see over here. Please help us to get rid of them, send uns an email, and don’t forget to include a screenshot of the advertisement and (important) the URL it directs you, otherwise we cannot block it.

Bundled installers from SourceForge (aka DevShare)

Speaking of SourceForge: lately we got repeatedly approached about bundled installers in SourceForge downloads. There seems to be a big misunderstanding related to this: It is true that SourceForge offers a revenue program called DevShare to projects hosted on their platform, which involves a bundled installer. However, this program is opt-in. As long as the developers of a project do not explicitly choose to take part in DevShare, SourceForge are not bundling anything with the installers.

We, the Greenshot development team, have decided to keep our installer clean, without a doubt, now and in future.

Further considerations

We are concerned about these alarming flows around free and open source software. This concern mainly relates to practices of reckless people or companies trying to make money on the back of open source projects and their users, but also (to some extend) to the advertising strategy of SourceForge. We are currently considering further steps like moving our installer downloads to another server where we have better control over the ads. Unfortunately, qualititive and reliable Content Delivery Network (CDN) hosting is not cheap.

We are not alone: the developers of the open source image editor GIMP no longer upload their releases to the SourceForge file system; for the sake of completeness and fairness, here is SourceForge’s statement regarding to this discussion.

Posted in Uncategorized | Tagged , , , | Leave a comment

How to Upload Screenshots to a Web Server via FTP, SCP or SFTP

WinSCP logo Ever needed to upload screenshots directly to a server using the FTP, SCP or SFTP protocol? Actually it is quite easy to harness WinSCP’s great scripting capabilities with Greenshot’s flexible external command plugin. This blog post provides a simple WinSCP upload script and explains how to make Greenshot call the script to upload your screenshot.

Sidenote: we know, a specialized plugin for this would be a nice thing to have. A WinSCP plugin is definitely near the top of our todo list, but it probably will not be available before Greenshot 2.0. So in the meantime the following method is a good alternative.

If WinSCP is not installed on your system yet, you can download it from, it is free and open source, too.
If you have not heard of Greenshot’s External Command Plugin yet or if you are not familiar with the Windows command line, you might want to have a look at How to use the External Command Plugin to send screenshots to other applications.

Configuring the upload script

It just needs a few lines to put together a WinSCP script that opens a connection, uploads a single file and closes the connection again – we have prepared a simple script for your convenience. Simply download the WinSCP upload script and store it on your hard disc. Of course, the script needs to know where to upload the files to, so you need to change your the connection settings (in the line starting with open) as well as the target directory on the server (starting with cd).

Testing the upload script

We recommend to test the script from the command line to see whether everything is alright. You can invoke the script by entering something like this into your command line:
"C:\path\to\" /script="C:\path\to\winscpupload.txt" /parameter // """C:\path\to\testfile.jpg"""
Of course, C:\path\to\ should reference the path to the files on your local hard disc.

If everything works fine, the script should output something like

batch abort
confirm off
Searching for host...
Connecting to host...
Using username "user".
Authenticating with pre-entered password.
Starting the session...
Reading remote directory...
Session started.
Active session: [1]
testfile.jpg | 80 KiB | 37,8 KiB/s | binary | 100%
Session '' closed.
No session.

Configuring Greenshot to call the upload script

The rest is pretty easy:

  1. Select “Configure external commands” from Greenshot’s main menu
  2. Click the “New” button and enter the following values
  3. Name: WinSCP Upload
  4. Command: C:\path\to\
  5. Argument: /script="C:\path\to\winscpupload.txt" /parameter // """{0}"""

Configuring external command for WinSCP upload script Take care of the correct syntax, especially the quotes: if there is a space somewhere in a file system path, you need to wrap it into quotes. The last part of “Argument” is literally """{0}""", including the 6 double quotes and curly braces. (Greenshot will replace {0} with the filename of the screenshot.)

That’s it. After confirming the new external command, you can use the WinSCP Upload option for future screenshots, from the destination picker or the editor’s “File” menu.

Posted in How-to | Tagged | Leave a comment

Greenshot 1.1.6 is ready for download

Not so long ago we have announced that Greenshot 1.1.6 is near, today it is here :)

It includes a few new features/improvements but is mainly a bugfix release, fixing some issues that have been reported for the previous version, especially for those who were having problems with Greenshot “forgetting” their settings now and then and for two problems that occurring when exporting screenshots to Microsoft Office.

The new version is eagerly waiting for you to download it, so don’t keep it waiting and get it from our download page.

Here is the complete changelog for Greenshot 1.1.6 – enjoy :)

1.1.6 build 2779 Bugfix Release

Bugs resolved (for bug details go to and search on the ID):
* Bug #1515: Changed the settings GUI to clearly show that the interactive Window capture mode doesn't use the windows capture mode settings.
* Bug #1517: export to Microsoft Word always goes to the last active Word instance.
* Bug #1525/#1486: Greenshot looses configuration settings. (At least we hope this is resolved)
* Bug #1528: export to Microsoft Excel isn't stored in file, which results in a "red cross" when opening on a different or MUCH later on the same computer.
* Bug #1544: EntryPointNotFoundException when using higlight area or blur
* Bug #1546: Exception in the editor when using multiple destination, among which the editor, and a picker (e.g. Word) is shown.
* Not reported: Canceling Imgur authorization or upload caused an NullPointerReference

* Added EXIF orientation support when copying images from the clipboard
* Feature #596: Added commandline option "/inidirectory " to specify the location of the greenshot.ini, this can e.g. be used for multi-profiles...
* Removed reading the greenshot.ini if it was changed manually outside of Greenshot while it is running, this should increase stability. People should now exit Greenshot before modifying this file manually.

* Printouts are now rotated counter-clockwise instead of clockwise, for most people this should be preferable (#1552)

Posted in Releases | Tagged , , | Leave a comment