Jeffrey’s “Export to PicasaWeb” Lightroom Plugin

Google has started to dismantle PicasaWeb, and many features no longer work. If you use PicasaWeb, you should migrate away immediately.

Google has stated that they have no plans to release an API for Google Photos, so a Lightroom plugin for Google Photos is highly unlikely to materialize.

This plugin allows you to export images from Lightroom directly to your Google PicasaWeb (AKA “Google Photos”) account.

This plugin works in Lightroom Classic, and older versions as far back as Lightroom 3, though some features depend on the version of Lightroom.

The same download works for both Windows and Mac. See the box to the upper right for the download link (in orange) and installation instructions.

Please see the FAQ and known issues before reporting bugs. If this is your first look at my export plugins, please see the announcement post for an overview and some important information.

When run in Lightroom 3 or later, there is full support for Lightroom's new Publish feature. See the manual for Publish to PicasaWeb for details.

Google Plus (G+)

Google doesn't yet provide an API for third-party apps to upload to Google Plus, but you can sort of get some G+ interaction via uploading through PicasaWeb; see this FAQ for details.


This plugin is distributed as “donationware”. I have chosen to make it available for free — everyone can use it forever, without cost of any kind — but unless registered, its functionality is somewhat reduced after six weeks.

Registration is done via PayPal, and if you choose to register, it costs the minimum 1-cent PayPal fee; any amount you'd like to add beyond PayPal's sliding fees as a gift to me is completely optional, and completely appreciated.

Note: a Lightroom major upgrade, such as from Lr10 to Lr11 de-registers the plugin in the upgraded version, so if you want to maintain registration, a new ($0.01 if you like) registration code is needed in the upgraded version. It makes for a hassle every couple of years, I know. Sorry. See this note for details.

For details on plugin registration and on how I came into this hobby of Lightroom plugin development, see my Plugin Registration page.

Version History
( Update Log via RSS )


Oops, more Lr7 stuff.


Probably one of the last updates for this plugin, since Google has abandoned PicasaWeb. This update allows the plugin to work in Lr7.


Added the Newline template token.

Enhanced the FolderName token

Added the "only if it has a value" feature to template tokens.


Added the following tokens to the template tokens that my plugins understand: Artworks, ArtworkTitle, ArtworkCopyright, ArtworkSource, ArtworkCreator, ArtworkDateCreated, ArtworkInventoryNum


Tell users that Google is shutting PicasaWeb down, so most things don't work anymore.


Uploads had suddenly stopped working, and it seemed like it was because Google had abandoned PicasaWeb, and that may still be the case, but thanks to Rob Jones over at Lightroom plugin provider New P Products for cluing me in on an upload method that still actually works.


Oops, yesterday's update caused all photos sent to Twitter to be marked as sensitive.


Retooled to use a new Twitter API, allowing photos not to take up any characters in a tweet.

Added the following tokens to the templates that my plugins understand: FileModYYYY, FileModYY, FileModMM, FileModDD, FileModHH, FileModMIN, FileModSS, FileYYYY, FileYY, FileMM, FileDD, FileHH, FileMIN, FileSS, Weekday, Wday, weekday, wday.

Fix for Lightroom 2. Support for older versions of Lightroom will be stopped soon.

Got around a situation where Lighroom would crash duing an export of large images.

Better dialog real-estate managment for the meatadata section.

Fixed a bug with the keyword tables in the LUA token.


Fixed how custom {People} formatting works with people keywords that have no birthday associated with them.

Try to avoid yet another place where Lightroom gets hung because it can't handle certain kinds of dialogs at the same time.

Fix to get around a Mac display issue with Lr6 on OSX.

Added Russian-langauge support for the People-Support {People} tag.

Added the {FilenameNumber} token to the templates that my plugins understand.

Some updates to support Lr2. Lr2 is sufficiently old that I will drop support for it soon.


Added ChildOf and DescendantOf filters to the {Keywords} and {KeywordsAll} template tokens that my plugins understand.

Fixed a bug with the 'edit saved credentials' dialog.


Well, I learned two new things today. One is that Lightroom doesn't filter bogus latitude and longitude data during import, and the other is that uploads to PicasaWeb with bogus location data fail very ungracefully.


Updated the Caption part of the dialog to show up to three lines of text, and the full text in the tooltip.

Added {SpeedKPH} and {SpeedMPH} to the list of template tokens supported by my plugins.

The {People} token wasn't working properly for some keywords without a registered birthday.

Updated Twitter support to better count lengths of tweets that include URLs.

20150612.281 Try to navigate better the rat's nest of conflicting data that is Lightroom's “understanding” of a photo's capture time.

Fixed the "SpecPeople:259: attemt to index al nil value" error.

UI fix for OSX 10.9

Fixed an assert-failure bug that could happen when editing a collection's settings.


In the POODLE-vunerability dialog, display a raw URL of a page on my site that discusses the issue, so that folks can be independently sure that the dialog is indeed from me and not malware.

20150130.278 Build Update.

Added support for the {People} template token, which works in conjunction with my People Support plugin to automatically include in upload captions and the like the names and/or ages of people in a photo.

Fix to the date_diff() function supported by the LUA template token.

The Plugin-Extras dialog to resend metadata could allow the [Resend] button to be pressed when no metadata was selected, resulting in confusion.

Updated the camera-name code to try to guess the actual camera model of Hasselblad H5D files, since in their infinite wisdom Hasselblad decided to encode three distinct models with the same internal code, making it impossible to know for sure what camera produced a given image file.


Added an "Export Location Override" section to the Publishing Manager dialog (when editing an existing publish service) that allows you to change the Export Location. I don't know why Adobe doesn't let you change it... it seems arbitrary.

Add a help dialog to the publish-services edit dialog to make it clear how to delete a publish-services collection.

Use a compressed view on the Plugin Extras dialog if the screen is not very tall.

Better debug logging of Twitter interaction.

Very long tweet text could break the dialog display.

Don't allow expert when we know ahead of time that the tweet is too long.

If twitter rejects a tweet (e.g. because it's too large), show the tweet and offer to allow the user to edit/resend at

Added extra logging to debug why Lightroom might fail to render for export.

When associating a Lr image to a PicasaWeb image manually, incorporate the actual posted time to PicasaWeb as the upload time in the photo history in Lr.

Registration was broken on Lr2

20141019.275 Windows Only: Add a one-time check for the POODLE security vulnerability, and alert the user if it exists.
20141010.274 Better error reporting with the visit-collection item in Publish.
20140923.273 Added the LrMD5, LrLocalization, LrSystemInfo, and LrMath packages to the {LUA} template token.
20140922.272 When deleting from a publish collection, properly maintain the 'Uploaded to...' metadata field.
20140902.271 New build system
20140820.270 Updating the name of an album to match a change at PicasaWeb didn't also update the visit-url. Does now.

Made the {GPSAltitude}, {Altitude}, and {GPSCoordinates} tokens subject to the geo-privacy settings like the other geo-related tokens.

Updated the Twitter support to allow my plugins' template tokens in the tweet text.

20140731.268 Registration fix for Lr5.6
20140729.267 Previous updates broke support on Lightroom 2
20140720.266 More Creative-Cloud support.

Fixed an issue with Creative-Cloud revalidation.


Lr5.5 and later Creative-Cloud installs can now revalidate themselves if needed.

20140710.263 Sigh, had a bug in the Creative-Cloud support.

Now supports Lr5.5+ Creative-Cloud Installs.

20140704.261 Sigh, introduced an error for some folks with the rebuild the other day.
20140630.260 Build-system update
20140618.259 Comments on published photos, when returned by Google to the plugin, can have HTML entities such that "It's great!" can become "It's great!", so try to reverse-code those back to plain text.

Added date_diff() and raw_time_diff() functions to the special {LUA} token understood by the plugin.


A missing 'automatic destination' could cause the plugin to crash.

Set up the ability to reauthenticate to your PicasaWeb account from the Publishing Manager dialog.

Add a note to the Keyword options to highlight that only exportable keywords are considered.

Removed the "location privacy" stuff from the metadata-management section of the dialog... it all appears in its own section, but I'd forgot to remove it here when I added it there.


Added new tokens to the template language the plugin understands: LrVersion, LrVersionMajor, LrVersionMinor, LrVersionRevision, LrVersionBuild, Location, CatalogName, CatalogPath, OperatingSystem, OS

Added new token filters: NS and LO

20140506.255 Fixed a "attempt to compare number with nil" error WRT album sort.

Fixed a bug in the "smoother revalidation" stuff recently added.


Added the "Recent PicasaWeb Comment" custom metadata item, which holds the date of the most recent comment for a Published photo, in YYYY-MM-DD format. While in the "Published Photos" section of the Library Grid, you can set the Filter to "Recent PicasaWeb Comment" and then scroll down to the end to see the most recent dates, and via that see the most-recently commented photos. It's a bit unelegant, but it's the best I can think of within the severe limits of Lightroom's plugin infrastructure.

Added a new "Location Privacy" section to the Exprt/Publish dialogs.

Updated the location-based tokens in the template language the plugin uses — City, State, Country, Location, Latitude, Longitude — to respect new privacy options in the Export/Publish dialogs, and in the resend-metadata dialog. You can override those options on a case-by-case basis with the evenIfPrivate filter.

Added locationIsPrivate variable to the environment available to the LUA token.

The {Empty} template token wasn't working properly.

Make the revalidation process smoother, especially for folks using Lr5.4 and later.


Enable a new feature internal to Lr5 for large exports that keeps the CPU from running too far ahead of the upload. Prior to this, Lightroom would go ahead and peg the CPU to pre-render all the images even if they weren't being uploaded at nearly the same speed. Now Lightroom pauses the behind-the-scenes rendering if it has gotten too far ahead of the upload.


A complete overhaul of the "Associate Images Automatically" code (in File > Plugin Extras > PicasaWeb Extras). It's still a fragile process, but it might work a bit better now.


Added (to File > Plugin Extras) the ability to check the remote status to see whether uploaded photos are still there, and clear out data from the catalog when they are not.

Added keywords to the list of metadata that can be imported back from PicasaWeb.


Gave the Publishing Manager UI some attention on Windows.

Added the “:EMBED” token filter to the template language.

20130926.248 Oops, fix a bug introduced in the previous update

Added a bunch of tokens to the preset templates supported: ExportFormat, ExportColorSpace, ExportBitDepth, ExportQuality, ExportSharpeningLevel, ExportSharpeningMedia, IpernityUrl, GoogleDriveUrl, and TumblrUrl.

The token-examples dialog had been broken. Also deprecated Folder and Path tokens in preference to FolderName and FolderPath tokens.


Work around a Lightroom bug concerning the determination of whether a photo is offline.


Update to reflect the new (but still undocumented) larger upload limit for photos: 100 megabytes / 50 megapixels.


Added the ability to import captions and map location from PicasaWeb back into Lightroom.


Made big updates to the "Export with Smart Previews?" section; you can now pick to be asked whether to export via Smart Previews, and can differentiate between when the Smart Previews are "good enough" for an export and when they are not.

Fixed the KW/KWE tables in template tokens; they had been broken when using load for the script.

Better handle very long user account names, so that the [Logout] button doesn't get cut off of the Export dialog.


Added an "Ask" option to the "Export with Smart Previews?" section, so one can be alerted to the situation at each export.

Moved the "Export with Smart Previews?" dialog section to a more-logical place in the order.


Work around a bug that causes the export-related progress bar to not show up right away.

20130629.240 Added an error report to aid in debugging why publish association might fail.
20130613.239 Better support for plugin revalidation.
20130611.238 Sigh, previous update for Lr5 broke things for the Lr5 beta.
20130611.237 Yet another Lr5 update
20130610.236 Better logging to try to understand catalog-write-access contention under Lightroom's hood
20130531.235 Made the "fetch my list of albums" operation substantially more efficient for users with a lot of G+ shares.
20130524.234 Apparently, a recent change broke things on Lr2, which some folks apparently still use.

Added the ability in Lr5 to export images even if the master image file is not available, so long as there's a smart preview available.

20130501.232 Update for Lr5
20130412.231 Fix to the Twitter fix.

Can now have Publish collections renamed to match album names changed at Google.

Sigh, Twitter yet again made an unannounced undocumented change to their API that immediately breaks apps that have worked for years, and doesn't even bother alerting developers after the fact. Lord knows how many developers wasted how many hours trying to debug something that should have been announced on the developer's blog. Days later, it's still not announced there. Twitter is not worse than Facebook, but seems to be trying.

20130328.229 Fix for the registration system.

Export could crash if a too-big-for-the-remote-service video upload was attempted.

Fixed a possible plugin crash in Lr2 that might happen if the remote site's servers are failing.

The account upgrade from "PicasaWeb" to "G+" that Google forces requires Lightroom support not found in Lr2, so tell the user that instead of just crashing.


Added support for some new template tokens: FlagStatus (requires Lr4.1 or later), and for Lr3 and later, a bunch of IPTC extended metadata: AdditionalModelInfo, CodeOfOrgShown, DigImageGUID, Event, ImageSupplierImageId, MinorModelAge, ModelAge, ModelReleaseID, ModelReleaseStatus, NameOfOrgShown, PersonShown, PlusVersion, PropertyReleaseID, PropertyReleaseStatus, and SourceType.

20130214.226 Small fix for Lr2
20130209.225 Update to handle new Twitter url-length settings.
20130206.224 Update the Twitter-related code to handle their new API. Their old API goes away next month.

Added the ability to use "automatic destinations" (the naming of target galleries based upon image metadata) in Publish. It's been in Export for years (as illustrated in this 2008 article on backing up), and you must create the destination presets from Export, but you can now access them in Publish.

Added the ability to set the caption on a one-off basis by just typing it in, avoiding the need to make a preset each time.

20121222.222 Seems there's a Lightroom bug for Lr4.3 on Windows tickled by the previous update, causing an error when uploading a replacement. This update untickles the bug.

A lot of work on the upload data path, making it more efficient and restoring the ability to retry the attempt on certain errors.

For Lr4.3 and later, greatly enhanced the efficiency of replace operations (e.g. when republishing an image).

Added automatic retry for the new mysterious Google response “UNAVAIL (GumbyTask: Fife status=APPLICATION_ERROR, message=/BlobService.CreateBlob to : APP_ERROR(7) MigrationProxy BaseOperation rejected because maximum thread pool capacity was reached.)”.

20121205.220 Added some debugging.
20121203.219 Add a link to the FAQ for the "missing destination cookies" error.
20121020.218 A recent optimization for Lr4 broke support for Lr2.
20121017.217 Plugin was blocking export due to DPX-video format in some cases where Lightroom didn't allow the format to be changed.
20121014.216 Added a help dialog when encountering the mysterious 'handle in the wrong state' error.
20121010.215 Fixed Twitter authentication.

Workaround for an "attempt to call field 'getProgressScope'" bug introduced in Lr4.2.

Enhance the {EMPTY} template token so that it interrupts the squelching of superfluous joining characters.

Disallow DPX-format video export, since that totally breaks things.

20121002.213 Keywords weren't being sent properly... likely broken since v209 )-:
20120902.212 Fixed some issues surrounding the "Create Album" dialog in Publish.

Updates to the environment in the {LUA} token (in the template tokens in my plugins) to include photoTime() and currentTime(), and other changes to match the updated docs at that link.

20120816.209 Throw an error if a caption is longer than Google allows, or if an image has too many keywords.
20120723.208 Fix (I hope) an "attempt to index a nil value" error.

Better reporting when you're out of quota at Google when trying to replace an image.

Oops, a side-effect of recent changes caused the log to bloat with a binary dump of exported images. Fixed.

Wow, it seems some people using Lr2 are still using very old versions of Lr2 that aren't up to snuff feature/bugfix wise. I don't want to support gratuitously old stuff, so I put a minimum of Lr2.6 to use the plugin.


In Lr4+ you can now create albums from the publish-service context menu, and also create "collections sets" for local organization of your publish collections. (You can't possibly imagine how difficult something so seemingly simple was to fit into Lightroom's Publish infrastructure.)


Twitter support now allows suppressing "Private" geoencoded locations in Lr4.1+

20120607.203 Very slow uploads of very large files in Lr4.1 could cause the new progress bar stuff to blow up.

It seems that Google creates a lot of spurious internal-use albums for some G+ users; these are now omitted from the album list shown in the plugin.

Discovered that the plugin was being inefficient when it fetched the album list from Google, doing so twice in a row. Now doing it just once, and in a much more efficient way to boot.

20120601.201 A corrupt image date could crash the upload at Google.

(See my blog post “Hidden Gems in Lightroom 4.1; Hidden Gems in Lightroom Plugin Development” for some details on what's new in this update for Lightroom 4.1.)

New upload engine in Lr4.1 that greatly increases the efficiency of large uploads. In Lr4.0 and older versions, upload handling is inefficient and large uploads can crash Lightroom, but from Lr4.1 you can easily upload up to PicasaWeb's max 20MB images and 100MB videos. (Note: PicasaWeb advertises videos up to 1GB, but you get that only when uploaded via the Picasa desktop app. The limit to third-party apps like this plugin is currently 100MB)

Due to remaining limitations in Lightroom, the plugin can use this more-efficient method only for initial image/video uploads, and not for replacements. The big win is for initial video uploads, so this is not a huge setback because Google doesn't allow videos to be replaced anyway (the plugin continues to silently ignores video updates).

With Lr4.1 and later, you also get an upload percent-complete report in the task progress bar, and the ability for upload cancels to take effect immediately.

Also added the ability to control whether geoencoded locations are sent along with the photo to PicasaWeb, and from Lr4.1 proper (the actual Lr4.1, not the 4.1RCs), the plugin knows whether a photo's location has been marked as private, so the plugin can now respond to that and exclude the geoencoded location in such situations. Options have been added to export and to metadata-resend operations; they default to excluding private locations.

Update to handle the Mac App Store version of Lightroom.

20120508.199 Yikes, Lr2 registrations were broken again.

Tweak for Lr4.1RC2.

Fixed the “photo too large to tweet” dialog message, which had been all garbled up.


Fixed a potential crash when processing some captions.


Added to the template tokens supported by the plugin: {FullMasterFolder}, {FullExportedFile}, and {FullExportedFolder}, and to match, renamed the recently-added {FullMasterPath} to {FullMasterFile}.


Enhanced the send-log dialog to hopefully make reports more meaningful to me, yielding, I hope, the ability to respond more sensibly to more reports.

Added {FullMasterPath} to the list of template tokens supported by the plugin.

20120410.194 Fixed the "Not authorized to view access private" error some folks got when switching among multiple PicasaWeb accounts.
20120404.193 Allow line breaks in captions.
20120330.192 Update to handle 4.1RC
20120327.191 More graceful handling of videos whose pixel size is not known.
20120326.190 Fix a "Credentials:200" error.

It seems Google has started to quietly roll out unannounced changes to user-account data that completely disconnects a user from their history in this plugin, so I've been scrambling to come up with a workaround so that years worth of work is not lost. This kind of firedrill wasn't quite on my schedule for the turbulent aftermath of Lr4's release, but such is life. This release contains a first stab at a data-migration utility that will help some. A catalog backup is recommended before taking the data-migration step. (A dialog will prompt you.)

No longer send the geoencoded location if metadata is marked to be removed from the exported copy.

20120309.188 Fix registrations in Lr2.
20120309.187 Handle better when authentication fails. Can now reauthenticate directly from publishing manager.
20120308.186 Update to the debug logging to better track down timing issues that might arise.

Lots more preparation for Lr4 (but still works in Lr2 and Lr3).

Lightroom's internal infrastructure doesn't handle large uploads well, and will most likely crash when trying to upload huge videos, so I've not added a warning and the ability for the user to decide when it kicks in.

Files that are offline are now detected before an export/publish begins, and if there are any, offers the option to abort the export, or just skip the offline ones. This is a lot more clear than the "dng_error_file_not_found" error you get from Lightroom if you follow through with an export attempt of an offline image.


Discovered why "metadata that triggers a republish" wasn't reliable, and fixed it.

20120214.184 Fixes an Lr2 issue introduced in the previous version.

A change in the previous version seemed to tickle a bug in the Lr4 beta that would see Lightroom lock up when the plugin was enabled with certain catalogs. I'm not entirely sure what the bug was, but in this release I've worked around what was tickling it.

Attempt to prepare for changes Twitter has announced will take place in how they return information about server errors.


More on the march toward Lr4, including upheaval in the code to handle Lightroom APIs being discontinued in Lr4.

Bumped up the minimum Lr3 version to Lr3.5, to ensure we've got those bug fixes. Lr2 and Lr4 are still supported, of course.

Added the {AspectRatio} token to the token templates understood by the plugin, and added the Length=num filter.

Be a bit more graceful in reporting when the target album of an upload no longer exists at PicasaWeb.

20120114.181 More tweaks for Lr4b

More attention to the new Twitter authorization code.


Removed the “Re-mark as Published” button from the plugin-extras dialog in Lr4, because Lr4 now supports this natively.

Moved the Twitter code over to a new style of Twitter authentication, in hopes that it cures the authentication problems some people have been having.

Moved all access of Twitter to HTTPS.

Removed an obsolete reference to from the Twitter help dialog.

Update for Lr4 beta: explain in the plugin manager that the plugin can't be registered in the beta.

20111222.178 Enabled export snapshot creation in Publish.

Better error handling for video export, and for when images/videos exceed upload limits.

Warn about the need to update the list of albums if it's not been updated for a long time.

The Lightroom bug referenced in the version note for 20110623.157 was fixed in Lr3.5, so I've removed the special workaround processing for that version and later.

20111210.176 Had issues with the registration button sometimes not showing

Google isn't graceful handling references to images that have been moved from an album that has since been deleted; I now try to get around that a bit better.

Updated how the Manual-association dialog is sized.


When doing a plugin upgrade, offer the ability to flush all the old copies of the plugin.

Fix an "attempt to concatenate field 'user_id_string'" error that pops up at rare times.

Added a system-clock check and reports to the user if the system clock is more than a minute out of date. An incorrect system clock can cause problems with website authentication, among other things.


Updates the account-authorization handshaking done with Google to handle some changes they will implement on Nov 15, 2011.

Include the account id (in addition to the full name that's already there) in the Publishing Manager login section, to allow multiple accounts associated with the same real name to be easily differentiated.

Reporting some errors can create a huge dialog box that can be difficult to close on OSX, so this update adds a [X] button in the upper right of the dialogs.

20111006.172 It seems that Google has a max limit of 50,000,000 pixels per photo.

Plugin would crash in some cases while trying to process Twitter-related settings.

Resending metadata could crash for images that had no GPS data

The "repopulate" function could fail with a "must be https" error.

Publish repopulation could fail with write-gate timeouts.

Google sends back "quota exceeded" errors in a non-standard way... detect these and pass along to the user more gracefully.

20110918.170 Previous update introduced a problem when trying to update a photo that has been deleted at PicasaWeb.

Reworked the innards to try to handle errors from Google more gracefully. (I wish Google's PicasaWeb API had a shred of consistency in how it reports errors. )-:

20110903.168 Added {PluginProperty} to the template tokens used by my plugins.
20110903.167 Work around what seems to be a bug in Windows that caused authentication to sometimes fail with a plugin crash.

Handle more gracefully the situation where there are no albums at PicasaWeb yet.

Display the PicasaWeb "nickname" instead of the (possibly-numeric) "username" in the "Logged in as" note.

Some internal optimizations to handle large gallery sets.

20110821.167 More updates for the big authentication change.

Due to the big change in the previous version, all authentications ("logins") from prior plugins had to be deleted and reauthenticated, but it seems I missed one place to warn the user. Hopefully this catches them all.


Huge overhaul of how the plugin talks to Google, moving to a new authentication system that should work with every type of Google account. (The authentication system the plugin used to use was the only one available when I first developed the plugin, but it doesn't work with some kinds of accounts.) I have immense respect for the folks at Google, both for what they do and how they do it, but the API to their photo service is patheticly haphazard... it really is not even in the same universe as the rest of what Google does.

Added the ability to include a photo when issuing a tweet via Twitter.

In the list of albums, added the ability to prepend the album type ("private", "protected", "public") to the name.

Gave the Twitter tweet input UI some attention.

Twitter automatically replaces URLs with their own urls, and the tweet-text character-counter now takes that into account, so pasting in urls of any length now "costs" a fixed amount (currently 19 characters for an HTTP url; 20 characters for an HTTPS url). The plugin no longer uses

Made it so that hitting ENTER while entering a tweet does not actually launch the export. This is a maddeningly-frustrating aspect of the Lightroom plugin infrastructure, but I've worked around it in a way that seems to work.

The 'refresh list' button was missing from the upload-destination list when it was configured to be a popup menu.

Google doesn't allow videos to be updated, so an attempt to republish them is silently ignored. Video metadata is updated.

Fixed "attempt to compare nil with number" error that some users might have gotten in Publish.

20110712.163 Had a minor plugin-crashing boo-boo in the previous update
20110711.162 Really long captions could cause a stack overflow.
20110708.161 Fix the "Export:663" error some have gotten.
20110706.160 Still struggling with catalog-access issues that seemed to have materialized out of the blue (with a bug in Lr3.4??). This update addresses creating a new publish collection.

The manual-association dialog was too big for some screens... now it auto-adjusts depending on the screen size.

More on the catalog-access errors that some are getting with Lr3.

20110703.158 For Lr2, fixes a 'must be called inside withReadAccessDo' error I'd recently introduced. For Lr3, tries to address a similar error that seems to pop up in rare cases.

There's a bug in Lightroom that causes it to sometimes include private keywords in exported copies. The plugin now detects these situations and alerts you to them, allowing you to avoid a privacy blunder.

20110614.156 Better error reporting for Google errors that we can do nothing about.

Better handle long album names by truncating at the beginning with '...', and having the tooltip be the full name.


Added a new section to the Publish Service settings dialog, on whether to refresh remote comments automatically or manually.

Be more robust to errors during the gallery-creation process.

Fixed a bug that caused the export destination to not properly refresh in response to selecting a preset in the export dialog.

20110513.153 Fixed a bug in how some export errors are reported.

Handle more gracefully the error that Google returns if you've changed your password since the last time the plugin authenticated itself.

Wasn't properly issuing an error message when used with Lr3.0 and Lr3.2.


Fixed some plugin-crash asserts that some new users might get.

Added "select all" button to Publish collection list.

20110329.150 Oops, the button to refresh the list of galleries had inadvertently disappeared.

Previous build was broken under Lr2, and some Lr3 installs.


Added the ability to create new PicasaWeb albums from within the publish manager.

Added the ability to sort the album list in the Publishing Manger

Added the ability to select which metadata items cause a Publish republish.


Added support for uploading videos. It's predicated on my guessing the MIME type of the video from the filename extension, so if you run into one I get wrong, please let me know.

Added the ability to manually associate photos to images at PicasaWeb, via the File > Plugin Extras > PicasaWeb Extras dialog.

Detect when Google throws up a CAPTCHA wall, and directs the user to be vetted by Google in their browser.

Added a progress dialog to the “Re-mark as Published” operation, so that it can be canceled, and to make it clear that something is going on under the hood.

Fixed a bug whereby one couldn't export via preset to an account different from the currently-logged in account.

The list of upload destinations was sometimes getting cut off


Added “Re-Mark as Published” to the Plugin-Extras dialog (“File > Plugin Extras > PicasaWeb Extras”). If you have published photos in the “Modified Photos to Re-Publish” grid segment, this moves them back to “Published Photos” without actually uploading anything to PicasaWeb. You might use this after making what you know to be a metadata-only change that won't affect how the image is shown at PicasaWeb.

Fixed a problem such that long album names caused buttons to become inaccessible in the export dialog.

Not sure what happened to the export dialog since I last checked it in Windows, but it was in need of some UI love.

20110116.145 Added Twitter support to Publish.

This version no longer works in Lr3.0 and Lr3.2 because many bugs have been fixed in Lr3.3: if you're using Lr3.0 or Lr3.2, please visit Lightroom's Help > Check for Updates to download the free update from Adobe. (The plugin also continues to work in Lr2.)

Added {CroppedWidth} and {CroppedHeight} to the template tokens used by my plugins.

Add a note of instruction to handle a (rare) situation where one needs to reauthenticate in the normal Export Dialog in order to get a Publish Service working again.

Be more graceful in certain no-response-from-Google situations.

20101217.143 Updated Twitter support for Twitter's new API endpoints
20101124.142 Fixed a crash sometimes encountered while updating remote-account data in the plugin.

Check whether galleries at PicasaWeb have been renamed from when publish-service collections were created, and prompt the user with a note that the renaming can be incorporated into Lightroom by enabling the "Forcefully rename current collections" option.

Replaced an ugly debug message that popped up when the plugin detected that a publish-service collection's related gallery at PicasaWeb has been removed from PicasaWeb, with a more user-friendly message.


Not sure when photo deletion started to fail, but updated the plugin to handle Google's response.

Be more clear about quote-exceeded messages from Google.


Fixes “Spec:343: attempt to index field '?' (a nil value)” error some were getting

Uses with more than 1,000 albums were getting the list chopped off... now all albums are shown, though album lists this large are pushing the limits of what Lightroom can handle.


Publish was sometimes getting stuck in a 'not logged in' state, if you hadn't refreshed your account data in the plugin for too long a time. Not sure why I might have built it that way, but I took off the time limit so now it shouldn't get stuck anymore. Wish I understood why I'd put it in in the first place, though. )-:

Warn about the loss of metadata if the "resize to megapizels" option is used.

20100830.137 When I upgraded the plugin to work with Google's JSON API, I neglected to handle login expiration in every place I needed. I think I've taken care of it now.
20100829.136 Made the revalidation process much simpler, doing away with the silly need for a revalidation file.
20100820.135 Discovered a bug in my plugin build system that caused horribly difficult-to-track-down errors in one plugin, so am pushing out rebuilt versions of all plugins just in case.
20100817.134 Added code to allow plugin revalidation after having been locked due to a bad Lightroom serial number.

Creating of a private gallery in the tools section didn't cause the gallery to be auto-selected for export.


Added an interactive filter to the album list in Publish; it'll show up if there are more than 10 albums. Only albums whose names match all the (space-separated) terms in the filter are shown.

Added the {KeywordsAll} template tag, for all keywords (like {Keywords}, but also includes those not marked for export).

A few users found some photos to always be "stuck" as Modified photos in a Publish collection. I'm still not 100% what might be going on and can't replicate the issue myself, but this version of the plugin tries some things to hopefully alleviate the problem.

20100715.131 There was a bug on Windows that caused the warning about potentially-excessive JPEG quality settings to lock up Lightroom for an indeterminate amount of time. Only way I could fix it was to move the warning to the metadata management section (where it doesn't belong as much as it doesn't belong where it was before, but Lightroom doesn't let me put it where it should go, next to the jpeg-quality slider). This also allowed me to put it back into Publish.
20100715.130 Yikes, the JPEG-quality thing I added didn't play well with Publish. Removing it from Publish 'till I figure out a better way.

Egads, the list of albums in the Publish Service dialog was not sorted.

Did a lot of work to revamp the ability to tie in photos already at PicasaWeb into your Lightroom catalog (and hence to populate a PicasaWeb publish service), working around bugs in Lightroom. See the new publish docs for details.

The plugin has long remembered your export settings from PicasaWeb export session to PicasaWeb export session, overriding Lightroom's desire to always bring your recent export settings from non-PicasaWeb exports. However, I had neglected to update the list of settings for Lightroom 3, so this is now corrected, and so the plugin now also remembers watermarking settings, file-renaming and photo-stacking, and DNG compatibility.

Clarified that the "delete all copies previously uploaded" option applies to, well, all copies previously uploaded, as opposed to some magic subset of copies previously uploaded that you might have fixed in mind.

Added a warning that blocks export when the JPEG quality is set needlessly high, referring users to my Analysis of Lightroom JPEG Export Quality Settings. You can bypass the warning if you like, and hide it forever, of course.


Discovered some rare and complex bugs related to collection renaming, and (I hope) fixed them.

Some users get "Unexpected resource version ID" errors when deleting photos, and while I can't replicate it myself, trying a blind change that might fix it.


Finally pushing the new version out of plugin beta (where it has been for a couple of weeks), after eight months of oft-painful development. It's extremely complex under the hood, so now that it's getting wider user and additional bugs are shaken out, there will likely be frequent updates... please keep an eye on the version history when you update.

Here are the update details from when it was in beta:

20100616.120 — This version can be registered in Lightroom 3. It can run in Lightroom 2 or Lightroom 3; it does not work in the Lr3 betas.

It uses my new registration system when run on Lightroom 3, which avoids some of the silly issues of the old one. Please take care to note the details on the registration page: use of this version (or later) of the plugin in Lightroom 3 requires a new registration code, even if you had registered some older version of the plugin.

Lots and lots of changes under the hood, including publish support in Lr3.

20100624.121 — Lots of bug fixes, and lots of new debug logging.

20100624.122 — Discovered a nasty build bug; pushing a new version in case it affects this plugin.

20100625.123 — Yikes, shaking out some more build issues.

20100628.124 — Had broken auto destinations.

20100629.125 — Lots of changes. Bolstered the separation between Publish and non-Publish exports.

20100629.126 — Lots more changes, especially related to auto destinations and replacing images. I sure wish Google would hire a few more PHDs to destupdify their photo API. Identified that "Import Smart Collection Settings" does not work for Publish, and corrupts things. Don't use it.


Added "STORAGE_UNAVAIL" to the list of mysterious Google replies that get auto-retried.


Added an automatic retry for when Google returns its mysterious "SERVER_ERROR" error.

Handled more gracefully a replace operation when the target photo no longer exists at PicasaWeb

Added some options to the Twitter <dest options> special code: add simple as an option to have it become just the name without quotes or other adornment; add short to par down the gallery name to just the leaf name. They can be combined, e.g. <dest short simple>.

Added some stuff to the LUA template token: a version of the standard os table (with date, difftime, getenv, es and time), and the standard Lightroom STK tables LrDate, LrPathUtils, and LrStringUtils). Also added a new functions TBL() (returns an empty table), ne(item) (returns true if the item is not empty), and nb(item) (returns true if the item is not blank; " " is blank but not empty, while "" and nil are both blank and empty).


Removed some Lr3-related debugging stuff that's showing up now that Lr3b2 is out. All plugin-related things should work in Lr3b2 except Publish, which will likely change drasticly between now and when Lr3 is actually released.

New when running Lr3b2 is a new "Snapshots on Export" section, which is basically a built-in version of this new plugin.

Added new tokens to the templates used in my plugins: IfKeyword and IfExportedKeyword are supported for Lr2 and later. For Lr3b1 and later the very powerful LUA token, and for Lr3b2 and later, a bunch of new localized date/time tokens. See the templates page for details.


Wholesale changes that attempt to honor the user's locale settings for numeric display (e.g. Europeans writing 3,14156 for pi). I've probably missed some spots, so let me know if you find some.

Added three new tokens to the templates that my plugins use, CameraName, IfGeoencoded, and Keywords. See the templates page for details.


Changed the semantics of the Places filter (in the tokens understood by the preset templates of my plugins) in two ways: if applied to a string value rather than a number, it works on the first number found in the string. Another is that you can now use something like Places=-1 to round to the 10s, Places=-2 to round to the 100s, etc.

Title presets weren't getting saved across LR restarts in some cases (for definitions of "some" meaning "all", sorry).


Oops, the upload date/time custom metadata items were swapped. Doh! With this new version, each catalog will auto-update to correct the issue the first time it's loaded. The format used for the date and time are restricted in Lr2 to whatever I've chosen, but the first time you load the plugin in the real Lr3 (whenever it comes out), the catalog will update itself again to write the dates/times in your user-customized, localized format.

Fixed the {GPSAltitude} template token so that it should now actually work.


Lots of updates to the Twitter support:

  • Better tweet-size estimates in line with recent processing changes at Twitter.
  • Added <caption> tag to the tweet-text template (it use the caption from the first image exported).
  • Added the ability to geotag tweets with a static location, or with the geoencoded location of the first image. A static location can be specified with a latitude, longitude pair, a geohash, or a url from a mapping service like Google, Yahoo, or Bing. On the encoded side, geodata embedded in the image can be used, or the geodata maintained by my geoencoding-support plugin).
  • You can now configure the plugin to shorten URLs via your own account, in case you want to track click-throughs yourself.
  • You can now specify that you want all URLs shortened. The default remains to shorten them only when required to get under the 140-character limit. You might, for example, want to forcefully shorten them all in conjunction with your own account, for click-through tracking.
  • The plugin now goes to great lengths to report whether a tweet is accepted by Twitter. In their infinite wisdom, the folks at Twitter suddenly decided to start ignoring long tweets instead of truncating them, but (here's the brilliant part) they still report back to the plugin that the tweet was successful. Sigh.

    Furthermore, they might also ignore (yet report as successful) other kinds of tweets, such as those that are a repeat of a "too recent" tweet. Those crafty folks at Twitter implemented these changes more than three months ago, but in a truly cunning move, they still detail the old behavior in their API documentation, making no mention whatsoever about how their service now actually works.

    Only by doing a bunch of extra work can the plugin detect whether a tweet was accepted or ignored. If ignored, there's no way for the plugin to know why, so at this point it merely reports that the tweet didn't go through.

  • Added the ability to control whether to send a Twitter tweet with photo keywords.

Completely changed how the one-click upgrade applies the newly-downloaded zip file, in the hopes that it'll work for more people. Rather than unzipping over the old copy, it now unzips to a temporary folder, then moves the old folder out of the way and the new folder into place. Prior versions' folders are now maintained (with the version number in the folder) in case you want to revert a version; you may want to clear them out from time to time. Of course, it won't take affect until you try to upgrade after having upgraded to or beyond this version.

Caught a few more Lr3b issues.

20100118.112 Added two new template tokens, {DaysSince} and {PhotoDaysSince}. They're a bit tricky, but could be useful.

Added the ability to set the date of an album while creating it, comparable to the feature added in v99 for automatic destinations. Also fixed a bug in that earlier code that made the minutes value of the album date wrong (though I don't think it really matters, because Google doesn't show the time-of-day on album dates.)

And it seems that I screwed up the previous version naming, pushing it out as 20100130.110 instead of 20100109.110, so the automatic version check for those running v110 will be fooled for the next month into thinking that there are no updates. These binary-looking dates are making me feel dyslexic. Sorry.


For some reason, Google no longer seems to be pulling the photo-capture time from an uploaded image, thereby falling back to the upload time as the "photo date". Perhaps it's just a bug, but in any case, the plugin now forcefully sets the photo date during the upload, so it seems to be working again.

I also figured out how to enable a "replace" function, so that you can update an image in place and not lose comments, etc.

20091230.109 Added a "Repopulate URLs" button to the Plugin Extras dialog, to allow correcting for the bug fixed in the previous push, and to correct for photos uploaded with old versions of the plugin.
20091230.108 Sigh, it seems 30,000+ lines of code are getting to be hard to keep track of, and I unintentially removed the exported url from the custom metadata (from the 'At PicasaWeb' item) a few versions back. This should fix it, at least for images uploaded from now.
20091216.107 Figured out when the "AgExportSession.photoExportSequence is obsolete; use photoIdExportSequence instead" error was coming from. A bug in Lr3 beta. I had to disable the export filter for the beta to avoid this.
20091216.106 Got a runtime error in the face of network failures. Now should be a bit more graceful.
20091215.105 Allow changing the font size of list of upload destinations. Those with long names might want to choose a smaller size to allow more text to fit on each row.
20091214.104 Added the special {NOJOINERS} token to the Template Language understood by my plugins.
20091210.103 Actually get the feature added in v99 to work.
20091209.102 A few small fixes for Lr3b, and tweaks to the extra-keywords stuff do tidy up repeated keywords in the display.
20091205.101 Minor internal debugging tweaks.
20091203.100 Turns out that Google has a 500 photos-per-album limit, so the plugin now reports it more clearly when that error is reached. I also put in something to retry the upload if the REJECTED_USER_LIMIT error is hit. I never run into it myself, so it's a shot in the dark whether the new code will actually work, and it's still debatable just what "REJECTED_USER_LIMIT" actually means, since Google does not seem to document the errors they might send back. We'll see.
20091123.99 Added an option in the auto-destinations stuff to set the date of auto-created albums to the date of the first photo.
20091118.98 Added an {Altitude} item to the templates understood by the plugin. It's the numeric altitude in meters, as opposed to the {GPSAltitude} item which is a description of the altitude along the lines of 32.7 m. Also updated the Places filter so that it can be used on fields that merely begin with a number.
20091023.97 A bunch of UI fixes for Lr3b, such as fixing the scrollbar and the token-examples dialog.
20091022.96 Added a first draft of some rudimentary support for Lightroom 3 Beta. See this important note about plugin support in Lightroom 3 Beta and Lightroom 3, including future plans for features and my registration system.
20091014.95 Followup correction on yesterday's push.
20091013.94 Google seems to be having all kinds of troubles with their servers and the delete-photo operation. This push tries to work around them so that the "Delete copies previously uploaded" option doesn't cause the upload to abort.
20090916.93 Some UI tweaks earlier in the month had an unintended side effect of breaking the "choose destination at export time" feature. Sorry... fixed! Also, added some prose to make it more clear that the "create gallery" part of the choose-destination-at-export-time dialog is not part of the export process, but merely a tool placed there for the convenience of those wishing to create a new gallery just prior to exporting.
20090915.92 Fixed some keyword-related issues. First, due to a silly bug on my part, there had been an artificial limit on the number of keywords sent. Second, also due to a bug on my part, the keyword order was scrambled. The plugin now sends them in the order Lightroom provides them (which seems to be alphabetic). (Sorry to everyone who couldn't contact my server for the last few days... it had "issues", that are now fixed.)
20090905.91 Turns out that Lightroom has a bug in its XML parser on OSX that was tickled by yesterday's push. I've worked around it in this one, and filed a bug with Adobe. Sorry for the hassles.
20090904.90 I'm back from a long trip and starting up the plugin machinery again. This push addresses a small issue reported today that causes ampersands in your display name to show up incorrectly. I had been fairly sloppy in how the plugin processed user data from Google, but now I've done it in the Right and Proper way. Hopefully I didn't break anything along the way. 🙂
20090717.89 Fixed a "wrong number of arguments to insert" bug.
20090716.87 Sigh, Twitter engineers treat developers like a bunch of twits. Twitter just made a sudden, unannounced, and undocumented change to how they allow external applications like this plugin to connect to Twitter, breaking every external application out there. If a plugin follows the Twitter documentation, it will not work. I couldn't believe Twitter engineers could be so inexperienced or hostile (which?) the first time they pulled a stunt like this, but again? This is ridiculous... are there kids running the shop over there? If they do this again, I may just yank Twitter support from the plugins... it's not worth the frustration. For the time being, this push should fix things.

Completely rewrote how the “extra tags to send...” line is parsed. It could sometimes be a bit wonky, especially when template tokens were used, but hopefully it's more solid now.

Speaking of the template tokens, I added a bunch more somewhat esoteric things, filling out all the metadata items available to the plugin. Something like “Workflow Job Identifier” might not be all that useful, but if you repurpose a field with my metadata-viewer preset builder plugin, these otherwise esoteric items may prove to be useful. For example, I've relabeled the Job Identifier field as “Blog Url” in my custom view, and can now use the {JobIdentifier} token to refer to it.

I redid all the code on squelching joining characters to make more sense (I hope), and included <br> and friends (e.g. <br/>) as special joining characters that should magically do the right thing. Also added colon as a joining character.

Enhanced the one-click upgrade stuff quite a bit, now detecting ahead of time when it will fail because the plugin is installed where Lightroom can't write (if Lightroom can't write to it, it can't update itself). I also added a progress bar, and now download in smaller chunks to avoid 'out of memory' errors on the larger plugins. Do remember that this new functionality becomes available after you upgrade to or past this version, when you then upgrade with it.

Fixed that during an upload of a single image, the progress-bar status didn't reflect when the image was being uploaded (it said "rendering..." the whole time).

Added a defensive error check: try to detect some of the weird error messages that the OS returns when a firewall blocks Lightroom from using the Internet. You'd be shocked to hear how much time I spend telling people "check your firewall and enable an exception for Lightroom...". Hopefully this'll stem that stream.

20090616.85 Sigh, this upload-destination fiasco is a real pain. Maybe have it nailed down this time.
20090615.84 Some people are still having images uploaded to the wrong album, and I'm starting to think that it's a case of corrupt Lightroom preferences. I've looked at some logs and it seems to be a case of "this can't possibly happen" happening. I've added something in this version that kills some old information with prejudice.... if this doesn't take care of it, please send a log again (via the "Send to Jeffrey" button in the upper-right of the plugin manager), but I suspect my reply will be to ask you to blast your LR preferences file and start over.

Sigh, it turns out that a few days ago, Twitter suddenly changed authentication methods in a way that was guaranteed to break every strong-authentication application (such as this plugin). Sigh. This update handles the new authentication style, and includes better error reporting for the next time they pull a stunt like this.

Fixed progress bar during upload.

Added a couple of new custom metadata fields, "PicasaWeb Upload Date", and "Upload Time". The former can be used in the Library Grid Filter to sort/select/filter by the date you uploaded to PicasaWeb.

Because the new custom fields mean a change to the database, the first time you load this new version, Lightroom will pop up a dialog asking "Update catalog for plug-in?" to which you'll want to answer yes ("Update"). Then a progress bar will show up and, if you have a lot of photos in your catalog that had been uploaded to PicasaWeb, will just sit there for potentially several minutes, looking stuck. Just let it work. For my catalog with 48,000 photos, it took about 5 minutes.

I'll add these to my Metadata-Viewer Preset Editor plugin soon, but for those maintaining their own viewer tagsets, these can be found at info.regex.lightroom.export.picasaweb2.uploadDate and ....uploadTime.


Well, here's something new: Twitter support. It may be a bit iffy, mostly because I don't use Twitter myself, so perhaps I've missed something about the culture in which it's used, but I've added something that allows you to send a tweet after a successful upload, with a mini template language that allows you to include a photo url or destination-set url in the tweet.

The plugin uses Twitter's new strong secure authentication, so you don't even have to tell the plugin your username or password. You authenticate at Twitter and grant the plugin application permission to send tweets on your behalf.

A note to fellow developers, who will feel my pain: in order to get this strong-secure authentication support working, I had to code up SHA-1 Secure Hash computation from scratch, in pure Lua... a horrid language, I'll remind you, that has absolutely no bitwise operations, or even integer support. No masks, no bitwise xors, no way to test bits or shift words or any of that stuff. As I coded it, I felt as if I were chiseling NAND gates from rough blocks of silicon.

I felt quite the achievement once I got it working, but only then realized that I also need to code up my own HMAC-SHA1 secure signature routine. It's less involved than the original SHA-1 stuff, but again, filled with bytewise xors. Fun stuff, in a very old-school way.

20090521.81 Sorry, another quick bugfix. It seems an internal change I made to try to get around a bug in Lightroom wasn't quite ready for prime time. Hope it is now.

Fixed a "loadstring" error some users got.

You can now use the scroll wheel with the scrollable lists (such as for the album list)... sort of. It works while the mouse is actually hovering over the scroll bar. That's the best I can figure out so far... it's better than nothing if you're a scroll-wheel user.

Added some new token filters to the preset templates used for things like extra tags and image captions: They're listed in the docs, but include new items like UCFirst capitalize first character of the item, or LC to lower-case the entire item. For example, if you want to include the city as an extra tag, but prefer your tags to be all lower case, you might use {City:LC} in the extra-tag dialog.

20090519.79 Fixed an album-creation bug I introduced recently, and added the hard-coded PicasaWeb's image-size limit of 20MB, so you'll be informed before upload that it's too big.
20090518.78 Somewhere along the way the plugin stopped updating the progress bar as it worked. I've restored it, so now you can see it inch along as the uploads complete. I also included some stuff to communicate with the next version of my Metadata Wrangler plugin help coordinate a canceled export. Unfortunately, if you cancel an export, Lightroom does not tell filters like the Metadata Wrangler, so it blindly continues trying to process images that will not show up. I've added some hooks here to help the next version of the Metadata Wrangler detect a canceled export and not complain. It's imperfect, but I'm hoping it'll help.
20090510.77 Added a link in the Plugin Manager to the plugin's update-log RSS feed.

Added items to the title/description presets: ZenfolioUrl, SmugMugUrl, and FlickrUrl. If you have previously uploaded this image to one of those sites with my plugin that uploads to those sites, you can refer to that copy of the image by reference. Using the tag alone, e.g. {ZenfolioUrl}, it becomes the raw url, or nothing if the image wasn't previously uploaded. Using a =text argument inside the tag turns it into a link with the given text, e.g.

    See the {ZenfolioUrl=photo at Zenfolio}.


    See the <a href='...'>photo at Zenfolio</a>.

if the url is known. If the url is not known, the tag is replaced with nothingness, so you might want to include an "|..." fallback section, such as:

    See the {ZenfolioUrl=photo at Zenfolio|"photo at <a href=''>my Zenfolio site</a>"}.

The entire double-quoted part after the "|" is used when what comes before ends up being empty. In this case, that double-quoted part is some text that includes a link to a Zenfolio user's home page (you'd want to put yours, of course). So, if the url isn't known, the entry becomes

    See the photo at <a href=''>my Zenfolio site</a>.
20090429.75 Fixed a bug that could potentially crashed the plugin while editing caption/title and auto-destination presets.
20090425.74 Tweaked how the plugin tries to update itself during the one-click upgrade process, to hopefully get things working for those few Windows users that have never had it work. Crossing fingers. We'll see.
20090422.73 Fixed the caption preset stuff to disallow editing of the built-in caption presets, and added a note to that effect in the preset editor. I also reset the 'None' preset to an empty value, just in case it had gotten edited in a prior version of the plugin. Sorry it took so long to get around to this fix.
20090422.72 A few minor housekeeping updates: the 'enable enhanced debugging' checkbox in the Plugin Manager now turns on logging of all web traffic. It'll be useful if I ask you to send a log, but you probably want to leave it turned off during general use. I also added an icon to the registration page to reinforce what plugin is being registered.

Corrected the photo-date related items in the preset templates to properly use the dateTimeOriginal metadata field, rather than the edit-time dateTime field. It now uses the first of the following that it finds with a value: dateTimeOriginal, dateTimeDigitized, and dateTime. This bug was reported to me long ago, but I let it slip through the cracks, sorry.

20090402.70 Added scroll-one-line arrows to the top and bottom of the scrollbars, to allow fine-grained control of scrolling very long lists. (I've been programming for almost 30 years, but this is the first time I've ever built a graphical scrolling system from scratch, so I may be a bit slow on the uptake at times 🙂 )

Turns out that there's a bug in Lightroom that causes login names to be rejected if they can't actually fit in the input box that's presented when trying to log into a second account. To get around this bug for the few who run into it, I've made the box as wide as I can... I hope it's sufficient.


Big UI changes in some areas. I've cobbled together a way to add what appears to be a real scrollbar, so I've replaced the kludgey scrolling solution I had before. It seems to work okay.

I also changed the "Token Examples" dialog from paging to use the new scroll stuff.


It seems that PayPal doesn't give everyone a "Unique Transaction ID" in the registration confirmation mail; some people get a "Receipt Number". So, the registration dialog now accepts that as well.

I also removed the "Resolution value to record in metadata" control in the Metadata Management section. That had dated back to a time when the resolution setting was not available in the standard "Image Sizing" section of the export dialog, and I forgot to remove my custom one when the standard setting appeared. It was sort of silly having two controls for the same thing, sorry.

The resolution setting is still utterly meaningless unless you use it to actually compute the pixel size of the image (that is, if you have the "resize to" setting to something other than "pixels"). Once the image has been created, it's just a hint about how you intend it to be rendered when printed, but it has exactly zero impact on the quality that can or can't be achieved when printing.

20090310.66 I've added a popup dialog that appears the first time you install this plugin that explains how to activate it from the Export Dialog. It's currently not very “discoverable” (in UI lingo), and it leaves a lot of people befuddled. I hope this helps to stem the flow of “I can't get it to work” messages I get each day. I've begged Adobe to tweak the UI to make it more clear in the future.
20090305.65 Fixed a bug that caused the plugin to crash (and stay crashed across Lightroom restarts, even!) when deleting the caption preset that was actually chosen for the caption.
20090303.64 If there's an error calculating the automatic destination for a photo, now actually reports that error instead of just crashing
20090302.63 Fixed a bug that could cause the plugin to crash when using the File > Plugin Extras
20090228.62 Fixed a bug that caused a plugin crash if my server couldn't be reached during registration.

NOTE: you may need to restart Lightroom after installing to this (or a later) version from the previous (or an earlier) version. Please try a restart if you get an error the first time you try to use the plugin.

As per the ongoing discussion on my blog, with this version the plugin moves over to a "donationware" model, in which the plugin remains free, but registration eventually becomes required (and an eventual donation hoped for 🙂 ).

For details, see Lightroom Plugin Development: Now With Added Encouragement. (For info about what drove this decision, see What To Do When a Hobby Becomes Work?)

The plugin no longer expires, and correspondingly, I will not pay much attention to reports of bugs that have already been fixed, so please check your version and the version history before submitting bugs or feature requests.

There was a lot of internal upheaval in the code, so I expect that some boo-boos my surface. If something breaks for you with this version, please let me know, but until I fix it, feel free to revert to the previous version.

Several fixes and enhancements in this release: It can now track multiple PicasaWeb logins, and you can easily switch between and among them. There have been a lot of UI tweaks to make things look more natural (but Lightroom's plugin infrastructure still places great restrictions on what can be done, so it's not like it's smoothly polished yet). It now has more robust error reporting in the face of network problems.

20090129.60 Small housekeeping update for the new locales supported by Lightroom 2.3. Added more info to the debugging log when an export operation begins, to help diagnose any subsequent problems with the export.
20090126.59 The new scrollable-list stuff didn't deal with ampersands very well... things should be better now. Also added tooltips to the list items so that the full text can be read even if the display is cut short, although ampersands may appear in duplicate (or quadruplicate, depending on the OS)... it just wasn't worth the effort to get ampersands right in the tooltip.

Okay, so I spent the entire weekend working on my own scrollable-list control from scratch, because the built-in popup menu is just not very easy to work with when one has a lot of galleries. I didn't have much to work with, and the result is a bit wonky, but it's much more usable when the list is long, so I'm throwing it out there. If you don't have a long list of export destinations, you can revert back to the original via the "configure list appearance" button. With that button you can also change how much of the list is shown at once, to suit your personal preference.

20090116.57 It turns out that the automatic upgrade stuff doesn't work if the plugin folder has been renamed from its original. That should generally not happen, but it's possible, so the plugin now checks its own location reports the issue to the user if it finds it.
20090115.56 Added more debugging-log stuff to the 'Upgrade Now' button action, to try to understand why it doesn't work for some people.
20090115.55 Added a 'click here to change the export destination' note to the masthead image, because some new users are confused how to change export destinations.
20090110.54 Added a checkbox in the Plugin Manager to turn on enhanced debugging (more stuff in the plugin's debugging log), and added a button in the same place that sends your log to me. Particularly for “the upgrade button doesn't work” and “error while uploading” type issues, this should be useful for debugging.
20081228.53 My preset dialog (for caption presets) was a bit wonky and didn't update itself when a preset was added. Fixed that. Also, in the export dialog proper, the example text next to the preset dropdown didn't auto-expand as the preset was changed. Fixed that, too.
20081224.52 The "Extras" item in the File menu had stopped working. Works now.
20081223.51 Bumping back the expiration date.
20081215.50 Small fix for some of the logging code.
20081208.49 Fixed a problem that sometimes caused errors during login/authentication, or after logging out.
20081204.48 Try to work around a fairly rare Lightroom bug that sometimes causes large exports to fail with the note Whoa, exported image doesn't exist after waitForRender by pausing for a few seconds to see whether the image shows up. If not, then you still get the error and the export fails.
20081128.47 Added the "auto destination" feature.
20081127.46 The counting of previous uploads (for the All/Update/New of the Upload Destination section) was not working right.
20081125.45 Another fix for a bug that had disabled plugin presets (for captions, etc.)
20081124.44 Perhaps fixed a problem whereby the "Upgrade Now" button didn't work for some Windows users. We'll see whether it works when those users upgrade from this version to whatever version is next.
20081123.43 Fixed a plugin crash when using the plugin's built-in preset system.
20081122.42 No problems from the upheaval recently, so pushing back the expiration a bit.
20081118.41 Fix album-creation bug.
20081117.40 Oops, wouldn't let you log in / authenticate if you weren't already. Doh. Fixed.
20081117.39 No new functionality in this version, but a huge upheaval in the underlying code to repair an unfortunate design choice I made early on in the development that had limiting consequences I'd not foreseen. There are likely bugs introduced in this version, and as such, it has a short expiration date to encourage updates as those bugs are reported and fixed. If you do run into an error, please send (via email) the log referenced in the upper-right of the Plugin Manager. Thanks.
20081113.38 Fixed yet another list-of-upload-destinations bug. There are sure a lot of edge cases here.
20081111.37 Fixed a crash that happened sometimes when there are not yet any preexisting destinations at PicasaWeb.
20081104.36 Perhaps squelch a spurious error dialog
20081103.35 I don't know what's causing the slew of networking problems that have been reported, but I've gone ahead and added a retry mechanism. It'll retry operations that failed due to network problems indefinitely, but you can cancel out of the retries if you like. If the problems are some kind of flakiness on the machine (somehow introduced in Lr2.1???) this may allow operations to complete.
20081031.34 Now works properly with the shadow GPS data maintained by my geoencoding plugin.
20081024.33 Added an option to not add Lightroom keywords as metadata when uploading images. This allows you to not send any keywords if you also have them stripped from the image itself, such as when enabling the "Minimize Embedded Metadata" option, or when stripping keywords with my Metadata Wrangler. This applies only to keywords in the Lightroom library that are marked for export; those not marked for export are never sent. (Also related, recall that due to a Lightroom bug, images in a catalog upgraded from Lightroom 1.x with Lightroom 2.0 lost the ability to export keywords until a fix is applied.)
20081022.32 Addressed (and perhaps even fixed) a bug introduced in the previous build.
20081021.31 Small update so that a stuck background version check does not disable the plugin. Added the ability to put the "select at time of export" item at the top of the destination list, as had been requested a few times. Added some items to the template language that had inexplicably been missing: {HH}, {MIN}, {hh}, {min}, {ss}.
20081015.30 Added back the ability to set the print size via DPI and inches/cm. I think it's more confusing than anything (because it has nothing to do with what size something gets printed at unless you take care to set the printer DPI the same), but someone asked for it and I should really leave it up to the user. The plugin now allows you to use any color space registered on your computer when generating images to upload. I don't think this will be useful for very many people, but perhaps it might be a benefit when combined with some printing services(?)
20081010.29 Changed the PicasaWeb login method to not exclude users of Google Apps (which, apparently, had been happening until now). Internal change to the user-agent string that the plugin sends when uploading, to better conform to web standards

I created a "Metadata Management" section in the dialog, and moved some things into that from other sections.

Fixed a race condition that sometimes caused the export destination to not appear in the synopsis of a closed "Upload Destination" dialog section.

Removed the "replace" option, which had been inadvertently displayed (but disabled) for everyone. Google's "replace" operation requires HTTP support that Lightroom's plugin API doesn't provide.

Moved the items in the "Upload Management" section into the "Upload Destination" section, since they are really quite related.

20080923.27 Sigh, just realized that the "check for new version" stuff did break in 2.1. Totally my fault, sorry. Fixed.
20080921.26 Oops, the ability to use my template tokens in the 'extra keyword/tags' area, that I added last week, didn't actually recompute the tags on a per-image basis, applying the tags computed for the first image to all the others. That's now fixed, and tags are recomputed with each image.
20080920.25 Enhanced the {Rating} token to allow {Rating=*} to create "*****" through "". You can put most anything instead of the asterisk, so you might consider {Rating=great } to end up with "great great great". Since these forms result in nothing for an unrated photo, you can use the "|" pipe to provide a default "when empty" value, such as "rating": {Rating=*|"unrated"}
20080918.24 Added the ability to use template tokens like {Filename} in the "extra tags" input box.
20080916.23 Update an error message to reflect an apparent bug in LR that causes LR to hand off a file to my plugin for upload before the file is actually available. This seems to happen when using LR/Mogrify or other filters. Updated the url shown in the "status" section of the plugin manager
20080916.22 Finally have the upgrade button working on both Win and Mac. Since I returned home last week, I now have access to both kinds of machine for the first time since Lr2 was released. I can sum up the 5 hours I spent wrestling with the unzip code in three word: I hate Windows. Microsoft owes me five hours of my life back. Note that you may have to install this one by hand in order to get the newly working upgrade button... it's the next upgrade that should be easy-as-click.
20080914.21 Added a few more descriptive tooltips to the example-token dialog
20080914.20 Oops, fixed a boo-boo introduced in the previous version.
20080914.19 Remember (again) the upload-destination across exports. It used to work, and I'm not sure when it stopped working, but it must have been really annoying while it was broken, sorry.
20080914.18 Fixed tokens "OriginalWidth" and "OriginalHeight" in templates. Added a bunch of new template tokens and a new token filter. Added a token-examples button, which brings up a dialog listing all tokens and their value for an example photo (the first photo in the export list).
20080905.17 Fixed an "undefined global: DestinationSynopsis" error that could happen when using a preset with a "select at export time" upload-destination setting
20080831.16 Handle a race condition in the upgrade logic that sometimes results in a superfluous "You have version XYZ, but version XYZ is now available" message
20080829.15 Added a bunch of new items to the template language.
20080829.14 Oops, left some debugging cruft that results in an "empty" dialog if the logged-in-user has no galleries or the like. Fixed.
20080828.13 Minor tweaks
20080828.12 A few more tweaks to report a failed upgrade attempt a bit more clearly
20080828.11 Whoo-hoo, finally figured out the "assert" problem that some people without albums were having. When upgrading, ignore a status of “50” (which means “out of disk space”) from the unzip the plugin performs. It seems Windows often reports this status even when there's plenty of disk space left, so until I can understand it better, I'll just ignore that code.
20080827.10 Fixed the Caption {Filetype} token (was broken for DNGs). Made some Layout tweaks in my preset dialogs. Added titles to the tools sections (were missing on OSX)
20080817.9 Lots of little tweaks as I cleaned things up. Added a bunch of stuff to the Plugin Manager, including a “What's New” button that shows up next to the “Upgrade Now” button when a new version is available. Removed the auto-destination stuff because I'm getting error-code 500 responses from Google with them. Will investigate.
20080814.8 Fixed infinite cycle of 'assert' messages one might get in odd situations
20080812.7 Fixes (I hope) a "bad argument #1 to '?' (table expected, got nil)" error
20080811.6 Moved and renamed the debugging logs to a temporary folder, and added log Show/Delete buttons to the plugin's custom section of the Plugin Manager.
20080806.5 Fixed {State} and {Rating} in preset templates.
20080805.4 Oops, the Windows versions had lost the ability to upgrade themselves. Once this version is installed manually, subsequent versions should be able to upgrade as discussed here.
20080804.3 Fixed "Access to undefined global: LrError" error that happens when trying to report a login-related problem.
20080804.2 Fixed a couple of internal errors related to the "choose destination at time of export" feature
20080729.1 Initial public release

All 300 comments so far, oldest first...

picasawev-20080729.1 does not work on my Lihtroom 2. I get information that there is something wrong in reading the schema. So the plug in is disabled. OS Windows XP.


— comment by Erkki M on July 30th, 2008 at 3:43am JST (13 years, 10 months ago) comment permalink

I get an error using this version on XP: selecting the file-export- a dialogue box pops up titled “info” with the text of “At line 13435”
clicking ok continues to the usual album dialogue and works ok from then.

Fixed in .2 —Jeffrey

— comment by Daniel on July 30th, 2008 at 5:42am JST (13 years, 10 months ago) comment permalink

LR2 “Update Catalog for Plug-in” message on first opening of catalog after copying files to the Modules folder. Win XP. Why is a catalog update needed?? I’ll update but am apprehensive…

Ah, I should have mentioned this somewhere. LR2 allows plugins to add per-image data such that it can be used in searches, smart collections, and filters, but to do so it has to update the catalog with the “schema” (information about what kind of data will be stored, and how it can be accessed by the filters, smart collections, and searches).

My “Export to….” plugins support all that, so the catalog is upgraded. Frankly, I don’t know why it’s something to bother the user about, but it does. You’ll get the same message if I add (or change) the list of possible per-image items the plugins saves.

I’ll go add something to the plugin-install page that mentions this. —Jeffrey

— comment by Morey on July 31st, 2008 at 9:57am JST (13 years, 10 months ago) comment permalink

Ah ha, Yes I see the “Uploaded to Picasa Web” in the metadata and in the new filter tool bar. Very Cool! I love this plug-in and use it ALL of the time. Thanks!

— comment by Morey on July 31st, 2008 at 1:48pm JST (13 years, 10 months ago) comment permalink

Also found a second dialog “Access to undefined global: LrError”

I have a picture of it. Send me an email and I can send it to you.

Fixed in .3 —Jeffrey

— comment by Brett Michaels on August 3rd, 2008 at 4:24pm JST (13 years, 10 months ago) comment permalink

For me it runs smoothly. No problem so far.
Thank you, Jeffrey!

— comment by Pacorramos on August 4th, 2008 at 1:17am JST (13 years, 10 months ago) comment permalink

Thanks Jeffrey! Works like a charm on WinXP SP3 + LR 2.0

— comment by Denis on August 5th, 2008 at 4:38am JST (13 years, 10 months ago) comment permalink

A little question: Would it be possible to change the logfile folder to other than “My Documents” (for instance, the same as the LR default plugins location)?

Moved to a temporary folder, as of .6 —Jeffrey

— comment by Pacorramos on August 10th, 2008 at 12:48am JST (13 years, 10 months ago) comment permalink

Works like a charm! Thanks 🙂

— comment by Gordo on August 12th, 2008 at 9:52am JST (13 years, 10 months ago) comment permalink


I’ve found your plugin really useful and I appreciate it a lot!

I have’nt found any bugs, I just have a small feature request.

When I upload photos to Picasa (or Flickr or Facebook) I start by creating a collection in Lightroom. And then I reorder the photos to get a better “story”. But it is not possible to select “user-order” when I upload. Would it be possible to add this feature?



PS I’ve used this workaround: 1) Export with custom name and three digit sequence number. 2) Reimport. 3) Upload in alphabetical order.

— comment by Nils Ohman on August 21st, 2008 at 5:36am JST (13 years, 9 months ago) comment permalink

I am using your picasa plugin with Lighroom in Leopard. I get the following error when I try to export images. No images to process. All were filtered out. Is this a bug?

Look at the All/Updated/New filter in the Upload Management section of the Export Dialog. You probably have it set to Updated or New, and have selected only images that have already been exported. —Jeffrey

— comment by MVB on August 23rd, 2008 at 12:36pm JST (13 years, 9 months ago) comment permalink

I’m finding that while the flickr plugin exports keywords correctly, applying country/city metadata the picasa plugin doesn’t convert/apply these data into keywords – I don’t think it’s LR2 as using the same photo the plugins export different keywords. I’ve tried w/ and w/out the hierarchical option checked. Not sure what could be causing this, does the picasaweb one not convert/export/apply location data to keywords?

— comment by Dan on August 26th, 2008 at 1:12am JST (13 years, 9 months ago) comment permalink

Works smoothly with LR2 and excellent instructions. Thanks! Windows XP.

I can’t figure out how to rate it on the Adobe Website, but will give it five stars if there is a way.

— comment by Wes Rishel on August 26th, 2008 at 2:10am JST (13 years, 9 months ago) comment permalink

It’s so great someone creates this free plugins! Thank you very much Jeffrey!

And one question: is it possible to upload your pictures without “tags” to Picasa? I want my tags in Lightroom, but I don’t want other people to see them online. I thought it was a feature before, but maybe i’m wrong?

Within Lightroom, you can mark each tag as to whether it should / shouldn’t be part of an export. —Jeffrey

— comment by Sam on August 27th, 2008 at 7:26pm JST (13 years, 9 months ago) comment permalink

Thanks so much for making your lightroom plugins freely available to everyone. I just sent you a little something to show my appreciation for your great service and outstanding workflow tools.

— comment by Tom G on September 3rd, 2008 at 12:26am JST (13 years, 9 months ago) comment permalink

Great tool,
but it would be even more great if it was possible to sort the list of album fetched from Picasa Web. I have about 30-50 albums and it is bit time consuming to manual search to list of albums.

So either, sort alphabetically or maybe search by typing.

Are the three options directly under the album dropdown (that allow you to sort alphabetically, by recentness of use, or by recentness of creation) not sufficient? —Jeffrey

— comment by Henrik on September 9th, 2008 at 2:15am JST (13 years, 9 months ago) comment permalink


First of all, thanks for the plugin!

One quick note–it doesn’t seem to be uploading all of the selected tags to Picasa Web Albums. Sometimes in lightroom I’ll have five or six tags on an image, but it will only upload two. If I retry and retry, it will always upload the same two tags. Any thoughts?


Are you sure it’s not the Lightroom keyword bug mentioned in the known issues? —Jeffrey

— comment by Robby on September 15th, 2008 at 4:51am JST (13 years, 8 months ago) comment permalink

Plugin Manager Update button doesn’t work for me.
– Open Plugin Manager
– Picasa Plugin reports Version xxxx is available
– Version yyyyyy is installed
– Click the [Upgrade Now] button. Upgrade In Place dialog is displayed.
– Click [Download & Install Now] button
– seems to work for a bit and reports Version yyyyyy has been installed.

The only way I have been able to upgrade is manually DL zip file, delete old and replace with new.

Windows XP SP3
LR2 obviously


Sadly, I had a bug in the auto-upgrade stuff in the old versions. It’s all fixed now, but people still have to upgrade manually to the fixed version to, er, get a fixed version. (By the way, I should point out that none of this upgrade stuff is built into Lightroom… the plugin does it all itself.) —Jeffrey

— comment by Morey on September 19th, 2008 at 9:44am JST (13 years, 8 months ago) comment permalink

Since .24 mine has been updating fine from the Plugin Manager. I too am on LR2.1 RC1.

— comment by Morey on September 23rd, 2008 at 12:54pm JST (13 years, 8 months ago) comment permalink

Downloaded version 20080923.27 and tried LR 2.0 plug in manager. The plug in manager wants some filed with a .lrplugin extension and there are none to be found. Am I doing something wrong or did I download the wrong file? Thanks.

The name of the folder left after unzipping ends with .lrplugin. That’s the plugin. —Jeffrey

— comment by Anthony Ahearn on September 24th, 2008 at 1:32am JST (13 years, 8 months ago) comment permalink

I can’t log in to PicasaWeb via your plugin:

Mac OS X 10.5.4
Lightroom 2.1 RC1

I suspect this is caused by one of two things:

1. The fact that I’m using an early release of 2.1; or
2. I have two Google IDs with the same e-mail address (the same one I used to submit this comment), which could be confusing your plug-in, or whatever Google service you try to authenticate with.

If it’s #1, then this might be an early preview suggesting your plugin might break for everyone when 2.1 is released. The rest of my post works with the assumption that #2 is happening (which seems more likely, for reasons discussed below):

* I have a normal “gmail-style” Google ID. This is what PicasaWeb uses when I try to log in on the web site (it only accepts this password with my e-mail address). Your plugin rejects these credentials as though they were invalid (BadAuthentication).
* I also have a “Google Apps for Your Domain” account with the same e-mail address. This account (password) doesn’t work with PicasaWeb. When I try to use this password with your plug-in, I get a very different error message:

PicasaWeb login aborted

It’s as though the service you’re trying to log into is confused about which version of my ID it should try to use, and when it (wrongly) tries to use the Google Apps account, either PicasaWeb or your plugin chokes.

This “duality” of Google accounts has always been a source of frustration, because applications can’t treat them as equivalent, and sometimes it’s not clear which one they should use if an ambiguity exists; please feel free to complain to Google if they’re doing something wrong here, or if poor documentation allowed you to do something wrong. Thanks for your help.

(With David’s help offline, I was able to address this. The fix appears in .29 —Jeffrey)

— comment by David Nesting on October 4th, 2008 at 11:08am JST (13 years, 8 months ago) comment permalink


Thank you for creating this file. I have tried a several times unzipping the file, it keeps telling me that the file is corrupted. Would you please help?

Thank you,

I’d suggest downloading again from scratch. It perhaps got corrupt during your first download. —Jeffrey

— comment by Carolyn on October 4th, 2008 at 1:36pm JST (13 years, 8 months ago) comment permalink


thank you very much. Using your plugins made my decision to actually buy Lightroom to organize my photos. You should get commission from Adobe. I have a copy of your regex book in my office, excellent work!!!


— comment by Christian on October 8th, 2008 at 7:24am JST (13 years, 8 months ago) comment permalink

Thanks for your plugins Jeffrey, they’re great since I try to use Lightroom 2 as a one-stop application to do everything. One thing though: when uploading a lot of pictures with your Picasaweb-plugin, somewhere in the process Lightroom returns this error:

+371.4: At =(tail call) line -1:
Return header ERROR

errorCode = “timedOut”
name = “timed out”
nativeCode = -1001

Any idea how to solve this? I got it with different series of pictures I tried to upload to a private picasaweb album. All have keywords, and I add a generic title for all pictures (basic text + filename), which appears under the pictures on picasaweb. Any ideas???

Timeouts are transitory in nature… they happen when there are network “issues” at your computer, at PicasaWeb, or in between. It would be nice if my plugin presented the error to you in a more graceful manner, and perhaps offered to retry instead of just dying. Generally speaking, my plugins aren’t very polished in the error-handling department, sorry. —Jeffrey

— comment by Bart G. on October 18th, 2008 at 3:29am JST (13 years, 7 months ago) comment permalink


This plugin used to have option NOT to upload Lightroom metadata and Lightroom Keywords. I really do not want my keywords to be uploaded.
Can you put this feature back, please?

Best regards, Filip.

It still does… you can strip most metadata with the “minimize” checkbox in the “Metadata” section. If you’d like more control, you can exercise a line-item veto of any item with my Metadata Wrangler plugin. —Jeffrey

— comment by Filip on October 19th, 2008 at 10:50am JST (13 years, 7 months ago) comment permalink

Hi, thx a lot for this Plugin – but

picasawev-20081015.30 does not work on my Lihtroom 2. I get information that there is something wrong in reading the schema. So the plug in is disabled?
i work with Windows XP?!?
Can you give me a hint??

thx and regards,


This sounds like perhaps a corrupt zip, or something like that. Just delete everything from the first install attempt, download again, and try installing again. —Jeffrey

— comment by toamau on October 19th, 2008 at 6:25pm JST (13 years, 7 months ago) comment permalink


First thanks for your plugin. I don’t know why, I have already exported several albums to my picasa web account with your plugin and suddenly, I have the following error :

?:13879: bad argument #1 to ‘?’ (string expected, got nil)

Do you have an idea ?

I have lightroom 2.1, I never had version 1. I tried to download the latest version, it is 20080905.17

— comment by Bruno Thomas on October 24th, 2008 at 6:13am JST (13 years, 7 months ago) comment permalink

Works perfekt with LR 2.1 and Vista SP2.
Great work!

Thanks a lot!

— comment by Andreas on November 1st, 2008 at 6:55am JST (13 years, 7 months ago) comment permalink


I want to develop a plugin for LR2.1 (1 workflow and 1 FTP).

Do you know where I can find resources and there is a book about the SDK?

thank you for your reply.

Many Thanks.

The only resources I know of are the SDK documentation and examples from Adobe, and the user-to-user forum. The docs contain a 187-page PDF full of details and examples. —Jeffrey

— comment by Baledent on November 8th, 2008 at 12:07am JST (13 years, 7 months ago) comment permalink

Jeffrey – What a great plugin. Many thanks for creating this and sharing it with us.
Best regards

— comment by Duncan Soar on November 20th, 2008 at 9:40pm JST (13 years, 6 months ago) comment permalink

The picasa plug-in (version 20081123.43) is estimating 5 hours to upload 255 RAW images. (using fast ethernet connection, Vista OS, fast computer). Is there a way to speed up the upload process? Thank you for developing this.

The time to upload is most strongly influenced by your internet connection. Fast connection means faster upload. (Personally, I have 100 megabit fiber to my house, but I still hesitate to use “fast” when uploading big images). —Jeffrey

— comment by Steve on November 24th, 2008 at 3:27am JST (13 years, 6 months ago) comment permalink

Hi Jeffrey,

Is it possible to automatically create a smart collection for each Album that I created in Picasa?

I can create it manually, but is it possible to automate it?

It’s easy to have one smart collection for all Photos, I uploaded.
It’s also possible to select only photos in one particular picasa album, by filtering by the name of the album. But how can I create one Smart collection for each Album I have uploaded to picasa and name it accordingly?


I’m using version 20081127.46

I’d suggest either using a special per-album keyword that you apply to each photo you want in the album, then make a smart collection based on that. You can then use the “Update” upload feature after selecting everything in the smart collection to ensure that all the images in the collection are indeed uploaded. But actually, the more straightforward approach would be to simply maintain a set of collections yourself, since that’s sort of exactly what they’re for.

In either case, to complete the process, it’d be easier if you could use the “auto destination” feature that I have on my other plugins (highlighted here. I guess I haven’t added that to the PicasaWeb plugin yet, so I’ll try to do that soon. —Jeffrey

— comment by Hendrik on November 28th, 2008 at 6:37am JST (13 years, 6 months ago) comment permalink

How do you clear the PicasaWeb Metadata in LR? I uploaded some photos and then deleted them in PicasaWeb and I want to have those changes reflected in LR.

Pull up the “File > Plugin Extras > PicasaWeb Extras” dialog. —Jeffrey

— comment by T.J. Powell on November 29th, 2008 at 11:17pm JST (13 years, 6 months ago) comment permalink

I can’t upgrade from 20081208.48 to 20081208.49 version. It downloads, then asks me to restart the plugin. I do and then it returns me to the start where it says I have v .48 and that a new version .49 exists. It cycles over and over if I keep trying. .49 never really seems to install. Any ideas what to do?

Also where do I enter my Picasa web account info? I can’t find a way to actually upload my files to Picasa.

— comment by Teaman on December 10th, 2008 at 4:28pm JST (13 years, 6 months ago) comment permalink

Is it possible to make this create albums which are sign-in on the privacy settings? I see it can create public and unlisted; Google recently added the Sign-in only viewing for albums and this would be great to create automatically.

Can you point me toward some docs? I can’t find reference to it in Google’s docs… —Jeffrey

— comment by Davi on January 2nd, 2009 at 1:58am JST (13 years, 5 months ago) comment permalink

Hi Jeffrey,
The only reference I can find is in the Google Support pages at – if you mean on the Google/Picasaweb API end I don’t have a clue as to where to start looking, sorry- Maybe someone else might know!

— comment by Davi on January 2nd, 2009 at 7:18pm JST (13 years, 5 months ago) comment permalink

Hello! What a great plug-in! great job there!
I wonder if there is a way to auto select the album date for picasa export! I am using the LR2 version!

— comment by Guilherme Nunes on January 8th, 2009 at 12:53am JST (13 years, 5 months ago) comment permalink

Thanks for the great export plugins. I have one question, I’m using with Lightroom 2.2 and I can’t seem to find a way to use Photoshop actions as a post-processing filter. I can add your Wrangler plugin but how can I use a PS action/droplet? Thank you.

Lightroom disables the post-processing actions when using a plugin as an export destination. That sort of makes sense because you’d be applying the Photoshop action after the photo is uploaded. I really should just port over my run any command piglet to Lightroom 2…… —Jeffrey

— comment by WakoNiko on January 19th, 2009 at 12:22pm JST (13 years, 4 months ago) comment permalink

Thanks for the quick answer… I’ve been looking all over the Internet and nobody seems to mention this issue. Looks like you’re the only one with a potential solution in your hands. I hope you will port run any command one day… Do you have any alternate suggestion in the meantime? I’ve tried to use LR2/Mogrify and specify my droplet there in the config screen instead of ImageMagick’s binary, but obviously that doesn’t work -must be trying to add parameters that the droplet doesn’t understand. I might be able to point to a .bat and strip the extra parameters and just send the filename to the droplet. Not sure this is gonna work, I will let everybody know.

As a side note, if ever you need a new export plugin idea… Would be great if you could do an export to Gallery!!!

— comment by WakoNiko on January 19th, 2009 at 1:17pm JST (13 years, 4 months ago) comment permalink

I have searched high and low but can’t seem to find anything that can help my login/conection issues with Picasa using your plugin after upgrading to LR 2.2.
I have tried trashing and re-dowdnloading, moving to a different directory and/or drive..

Thanks in advance,

Lightroom Network Error: “cannot ConnectToHost”

“Can’t connect to host” is a networking error. Are you sure that PicasaWeb and your internet connection were up? —Jeffrey

— comment by Dale on January 26th, 2009 at 8:12am JST (13 years, 4 months ago) comment permalink

Dale, you might be using special characters in your username/password. I know I had some problems with that before (with the old version of the plugin), I’m not sure how the new version behaves. I had to change my password to make it work, give this a try.

— comment by WakoNiko on January 26th, 2009 at 10:05am JST (13 years, 4 months ago) comment permalink

As a follow-up to my comment on January 19th, 2009 at 1:17pm, I haven’t been able to use LR2/Mogrify to launch Droplets or any other executable than mogrify.exe itself. Sorry if anybody else is looking for the same thing, but that doesn’t look possible at this time, or at least until there is a “launch any command” plugin that works as an export filter under LR2. I actually ended up changing the way I publish files on the web and I now use The Turning Gate plugins which are different than Jeffrey’s but also very nice. I’m not going to detail every step of my workflow, but I export my files under a special folder called “Web”, running my droplet on them as a post-processing action, and then run the TTG plugins to export them to an FTP folder. It’s really less painful to use than it sounds.

— comment by Wako Niko on January 28th, 2009 at 6:50am JST (13 years, 4 months ago) comment permalink

Hum, actually, about my last comment, Jeffrey has JUST posted a new “run any command” plugin so you can still use his export plugins with your beloved Photoshop Droplets! Think NoiseWare, Smart Sharpen, etc… Thanks buddy.

It’s at

— comment by Wako Niko on January 28th, 2009 at 6:59am JST (13 years, 4 months ago) comment permalink

Hallo, Jeffrey.
(plugin number 20090129.60)

Thank you very much for readding the former plugin feature


I couldn’t live without it. Now I can start to use your plugin again.


— comment by Filip Goc on January 30th, 2009 at 9:24am JST (13 years, 4 months ago) comment permalink

Hello, Jeffrey. I like and enjoy both your Flickr and PicasaWeb export plugins, that they’re very useful for me. I have only a little question: is there any chance they eventually could be full automatically updated without any user intervention?

Probably not. It’s generally considered rude for a program to update itself like that. I built the whole upgrade thing from scratch (none of it is built into Lightroom), and so it’s sort of fragile, and I still get occasional reports that it doesn’t work. Also, some updates are less stable than others, along the lines of “okay, I’m trying something here… let me know how it goes”, and each person should be allowed to decide for themselves whether to accept it or wait. —Jeffrey

— comment by pacorramos on February 1st, 2009 at 12:59am JST (13 years, 4 months ago) comment permalink


Whenever i try to use the export to picasaweb i get an error that says the operation timed out. nativeCode=12002

I am using Lightroom 2.2 64 bit on Vista 64 bit.

I looked at the connections going out of my computer with tcpview and i see it trying to connect to:

Any Ideas?


— comment by Peter on February 2nd, 2009 at 11:04am JST (13 years, 4 months ago) comment permalink

Thanks Jeffrey for your efforts, hopefully you are seeing a little play money now from your work! I just registered the Picasa plugin, it’s probably the best $10 I’ve spent in a while – It has saved my a lot of time and makes pushing family photos online effortless!

In that vein, is it possible to parse and import new keywords and/or descriptions that have been added in Picasa Web into Lightroom?

My scenario is this: I am scanning family photos, and would like to put my family to work adding situational and people keywords on PicasaWeb. Then every few weeks, I’ll point the plugin (or something) to the Picasa album to snarf new/changed keywords and descriptions to get them into Lightroom. Does the Lightroom plugin API even allow for something like that?

Thanks again!

These kind of things are definitely on the to-do list, but this one will be tough. Indeed, the Lightroom plugin API does not allow for updating of keywords, and even if it did, without a timestamp on when each keyword was updated (in both Lightroom and PicasaWeb), it’s hard to make a robust sync. But until LR allows for a way to get keywords in from outside, you’re sort of stuck. )-: —Jeffrey

— comment by Mike Wren on February 23rd, 2009 at 1:37am JST (13 years, 3 months ago) comment permalink

Hi Jeffrey-
First of all, thanks for the plugin! I downloaded it a while back and finally used it about two weeks ago to get a gallery up to PicasaWeb. I wanted to add some more pictures yesterday, but all of a sudden got a message that “This plug-in is not installed on your computer or is not functioning properly.” I saw that an upgrade was available and upgraded the plug-in, restarted LR2, same message. I deleted the plug-in and tried again, but no change. Any idea what’s going on?
I am using “Export to PicasaWeb 20090305.65” with LR 2.2 on a MacBook Pro.
Thanks for your help.
Are there any diagnostic messages in the lower-right section of the Plugin Manager? When you “deleted the plugin”, was that from disk or just from the Plugin Manager? If not the former, please try deleting the entire plugin folder, unzipping a newly downloaded copy, and repointing the Plugin Manager at it. (Sometimes, the auto-upgrade stuff can get all goofed up and it needs a full restart.) If it still doesn’t work, contact me via email… —Jeffrey

— comment by Paula on March 6th, 2009 at 9:49pm JST (13 years, 3 months ago) comment permalink

I am using the latest version of the Picassa plug-in in Lightroom 2.0. I’m not sure if I am missing something obvious or if this is actually a bug. However I figured I would report it.

If I make a smart collection and use the “Exported to Picassa” filter, Lightroom successfully identifies all of the pictures which I have exported to Picassa. Now, if I go to this collection and edit a file (Metadata, etc) and then re-export the updated image from this collection, the export goes just fine but for some reason it is REMOVED from the collection. I don’t understand why as it should still be tagged as ‘exported to picassa’.

If I then delete the Smart Collection and re-make it, Lightroom once again successfully identifies all of the images – included whichever one I just edited.

Does that make sense?


— comment by Ryan Martini on March 19th, 2009 at 11:02am JST (13 years, 2 months ago) comment permalink


Update on my previous comment – I don’t have to delete the collection to get the Smart Collection to re-recognize the images which have been uploaded to Picassa. If I exit Lightroom and re-enter, it will also figure it out. May just be a Lightroom Bug.

It sure looks like a bug. I’ll test it, and submit it to Adobe if need be.

Second comment: If I have an image which has been uploaded to Picassa, and I wen through the hassle of setting up the ‘faces/people’ things on the images in Picassa, is there anyway to update and re-export the image from Lightroom without losing all of the faces, etc that I added?

I don’t think the PicasaWeb API allows for image replacement (because I think I would have added a “replace” checkbox if it had been there when I first developed the plugin), but I’ll take a look and see… —Jeffrey

— comment by Ryan Martini on March 19th, 2009 at 11:09am JST (13 years, 2 months ago) comment permalink

Version 20090325.68
Hey, thanks for this plugin!
I export edited pictures to picasa, but the original, unedited versions were exported.
To recreate:
1. Edit a picture with the “Develop” tools of lightroom
2. Switch back to the “Library” tab
3. Select the pictures and export it
4. Picasa shows the unedited version rather the exported “fixed” version of the picture

In the “File Settings” section of the Export Dialog, did you have “original” selected for the Format? —Jeffrey

— comment by Joe on March 28th, 2009 at 2:27am JST (13 years, 2 months ago) comment permalink

Version 20090429.75
For some reason I can’t get watermarks on my photos when they export, I put the copyright in the meta data then when exporting i check add copyright watermark and still nothing comes up… how do get the watermarks on?


Lightroom’s watermarking support is very limited, and not at all influenced by the plugin, so I suspect that if you’re not seeing them, you wouldn’t see them even if you did an export to local disk. Two possible problems come to mind: you can’t control the color of the copyright notice (I believe it’s always white), and you can’t control the size. The size is always the same (something like 12-pixels), so if you export very large images that are white in the corner where the copyright notice is placed, you won’t see the minuscule white text on top of the white background. To put it bluntly, Lightroom’s support for this is pathetic, but then, it’s only a Version 2 product and so they can’t be perfect everywhere (or even anywhere). I’m sure Adobe will address this in a future version of Lightroom. Until then, you might find Tim Armes’ LR2/Mogrify plugin very useful. —Jeffrey

— comment by Essex Prescott on May 1st, 2009 at 6:39am JST (13 years ago) comment permalink

Mac OS. Lightroom 2.1. Picassa Web Plugin.

What are the reasons for a REJECTED USER LIMIT error when exporting to picassa web?

Thank you,

As far as I’ve ever been able to determine, no one knows why Google sends back that error. It seems completely random (which makes it completely frustrating). —Jeffrey

— comment by Barry on June 19th, 2009 at 4:49am JST (12 years, 11 months ago) comment permalink

Hi Jeffrey, I love your plug-ins! Would you take a look at my error?

OS: Windows XP SP3
Software: v2.3 539407 Camera Raw 5.3
Plug-in: Jeffrey’s “Export to PicasaWeb” Lightroom Plugin v20090717.88
Error: 11226: wrong number of arguments to ‘insert’

I only get the first picture exported on local disk, and the process stopped after the above error message appears. I have no problem using the LR’s original export features.

Doh, sorry about that. Typo on my part. I just pushed .89 to fix it. Thanks for the report. —Jeffrey

— comment by Puputabu on July 17th, 2009 at 5:36pm JST (12 years, 10 months ago) comment permalink

Hi Jeffrey, thanks for the quick fix (this might be the fastest response from the developer I ever experienced!) It works perfectly now!

Although it is working all the time but, when I update the plug-in it always give me an

“Internal Error: Can’t load “Version.lua” (cannot open C:\Documents and Settings\________\デスクトップ\download\picasaweb-20090714.86\picasaweb-jfriedl.lrplugin\Version.lua: No such file or directory)”

error, then if I restart LR the plug-in seem properly updated (as I’m getting “You have the latest version” when I hit the update button.) As long as it’s working nothing major but thought you might want to take a look.

Odd, it seems something went wrong with the upgrade? Could you try a manual upgrade, and see how it goes? If you still have troubles, please send me the plugin log (via the “Send to Jeffrey” button in the upper-right of the Plugin Manager). —Jeffrey

— comment by Puputabu on July 17th, 2009 at 6:00pm JST (12 years, 10 months ago) comment permalink

Hi Jeffrey –
I just discoverd your plug-in about a month ago and it has made my life so my easier. Thanks so much! I am using quite a bit and was planning to register in the next few days (says my registration is due within 10 days)

Untill last night it worked great. Now I am getting the following error message and cant upload anything to picassa.

AgNegative: render image: AgNegative: renderToFile:

I have the latest version: 20090717.89

Any suggestions?
Thanks, Petra

The “DNG file not found” error is from Lightroom, and well, it can’t find the master DNG that you’re exporting. Perhaps the volume it’s on is offline? In any case, I expect you’d get the same error if you did a vanilla export to disk… it’s a Lightroom thing, not a plugin thing. —Jeffrey

— comment by Petra on August 15th, 2009 at 12:38am JST (12 years, 9 months ago) comment permalink

I’m trying to export my images to Picasa and I have a number of Virtual copies with different exposure settings or some creative b/w settings. Only the main image is exported. If I select a virtual copy and choose export, the plugin says there are no images found that need updating. Is this a known issue?

Picasaweb 20090717.89 in Lightroom 2.4 64 bit

Hmmm, I’ll have to check. I’d think that each virtual copy is considered its own unique photo by the plugin (with the same filename, of course). I’ll take a look… —Jeffrey

— comment by Jesse Houwing on August 18th, 2009 at 6:34am JST (12 years, 9 months ago) comment permalink

Hmmm it seems that when I choose update and the original image is up there, nothing happens, but when I choose Add, the files are added none the less. Anyways. Files uploaded :).

— comment by Jesse Houwing on August 18th, 2009 at 6:40am JST (12 years, 9 months ago) comment permalink

Hello Jeffrey,

I’ve found you plugin very usefull to share pics with my friends via picasa. Unfortunately, I have discovered, that it does not transfer GPS location data to picasa therefore leaving me with terrible manual job.
LR used: 2.4 build 572242 Windows XP
Plugin: 20090717.89

Photos were taken with Eos 40D as RAW and geotagged with Geosetter v.3.1.16 (
GPS data is visible in EXIF data of the file (checked with ExifPilot), however I didn’t manage to see it directly in LR.

Actually, All EXIF data were ignored ano in info on camera or exposure are transferred to webalbums.

Hope you can fix it to further improve this great product.


The plugin does send it, but it gets the information from Lightroom, so if you’re not seeing it in Lightroom, that’s your problem. If you geoencode with an external app, you should do so before loading into Lightroom. Geoencoding after might work if you Metadata > Read Metadata From File…. give it a try. You can also geoencode within Lightroom with my geoencoding plugin. In any case, you must see the geoencoding in the Library (either via the normal view, or in the case of my plugin, the “shadow data” view) before uploading to Picasa. —Jeffrey

— comment by Mateusz Figat on August 29th, 2009 at 7:02pm JST (12 years, 9 months ago) comment permalink


Just to report a small problem with pseudo display on release 20090717.89.
I changed my pseudo in Picasa (not the pseudo used to login, the pseudo displayed on the picasa web albums page).
My pseudo contains ‘&’ character. In the export plugin, it is displayed like that : ‘amp;’
Thank you for this great plugin !



Fixed in version .90. Thanks for the report. —Jeffrey

— comment by Fabrice on September 4th, 2009 at 2:23am JST (12 years, 9 months ago) comment permalink

Hello. Bo here from Copenhagen. I was happy to find your plugins for Flickr and for PicasaWeb.

I am on a Mac with Snow Leopard, using LR 2 and using PicasaWeb plugin 20090916.93 which I have a smaller problem with.

I uploaded a batch at jpg quality 60, which wasn’t satisfying, so I was happy to see that the was a obtion to replace new upload with existing pictures (delete copies previously uploaded)

But apparantly it doesn’t work because I get the following error messages (for every picture)

unknown response (500) to delete query

Am I doing something? Or does this setting not work with PicasaWeb?

It worked for me… could be a temporary issue at Google. When I tried, the plugin had no problem deleting the previous version, and the new version showed up in the list of galleries at PicasaWeb, but when clicking through to the image itself, I got a 404. Because it showed up somewhere on PicasaWeb but not elsewhere, it seems evident that they’re having “issues”, so maybe you ran into a different version of that. If you get it again, please send the plugin log (via the “Send to Jeffrey” button in the plugin manager) and I’ll take a look, just to be sure. —Jeffrey

— comment by Bo Pedersen on October 12th, 2009 at 4:43am JST (12 years, 8 months ago) comment permalink

Hi Jeffrey,

I got the following error when trying to export several images to PicasaWeb in LR 3.0b.

“An internal error has occurred: AgExportSession.photoExportSequence is obsolete; use photoIdExportSequence instead”

I’m using 20091023.97.

That’s internal to LR, so I doubt there’s anything I can do about it except to chalk it up to “beta”. I’ll see whether I can reproduce it, and if so, will see whether I can’t get Adobe to address it for the real LR3… —Jeffrey

— comment by Chris K. on October 25th, 2009 at 6:33am JST (12 years, 7 months ago) comment permalink

I have dual boot on my PC, accessing the same lightroom library from the two OS’s. I registered two plugins on one OS, and they are “non registred” on the other OS…
Is there something simple to get the two plugins registered (by pointing on a common file or something) on both “sides” of my machine? (maybe just putting 0.01$ on each actually)
Thanks for your work
Plugins : Picasa export and the facebook export

Exactly as you suggested…. point to the same plugin folders from both sides (or to multiple copies of the plugin folders, one per side… doesn’t really matter). Enter the same registration code into the plugin manager on each side… it should all just work. —Jeffrey

— comment by Greg on November 10th, 2009 at 3:25am JST (12 years, 7 months ago) comment permalink

hate to bother, but 🙂
I am Lightroom user and have no need for Picasa EXCEPT for the new great face recognition.
I am looking for a way to transfer Picasa’s name tags into Lightroom.
Any help is appreciated!

— comment by Nose on November 12th, 2009 at 6:50am JST (12 years, 7 months ago) comment permalink

Hey Jeffrey! Enjoying your great plugins over here in northern California!

I’m using the PicasaWeb export plugin version 20091023.97 with Lightroom 2.5 on Mac OS. I want to make two PicasaWeb export presets: one that adds photos to a set album and another that adds them to an auto destination. However, I can’t seem to make two PicasaWeb export presets with different settings. Is there a way to do this?

You should be able to…. just set what you want for the first settings and create a preset, then set what you want for the second and create a new (differently-named) preset… they should each encapsulate their own settings. —Jeffrey

— comment by Vincent Mo on November 17th, 2009 at 6:52pm JST (12 years, 6 months ago) comment permalink

PicasaWeb export plugin 20091023.97
Lightroom 2.5 on Mac OS

I get a few photos uploaded before it stops uploading. I think it might be hitting an upload rate limit, in which case you might be able to watch for a REJECTED_USER_LIMIT error:

Google has similar rate limits on many of its apis, e.g. the Maps geocoding API. Is it possible to watch for this error and retry and/or rate limit the uploads?

The error I’m talking about here isn’t the STORAGE_UNAVAIL one, although I did get that one later when I ran out of PicasaWeb space. =)

As far as I can tell, both STORAGE_UNAVAIL and REJECTED_USER_LIMIT have nothing to do with the plugin or your account… they’re Google internal error conditions leaking out unmassaged. Consider them the same as “We’re down for maintenance; please try again later”. —Jeffrey

— comment by Vincent Mo on November 18th, 2009 at 6:29pm JST (12 years, 6 months ago) comment permalink

Hi Jeffrey,

I have same error reported here before while exporting to Picasa web:
AgNegative: renderToFile:
My version is picasaweb-20091118.98

I am able to export to local disk no problem.

Thank you.

I very much doubt that you can export that same file to local disk if you’re getting that error during some other export.
In either case, though, it’s something you should report to Adobe… that error is way more basic than any plugin — it’s from the core of LR. —Jeffrey

— comment by Alexei on November 21st, 2009 at 1:01am JST (12 years, 6 months ago) comment permalink

Hi Jeffrey,

It’s great working with your LR plugin’s. Now that Google has enabled collaborative web album, I would like to export directly from LR to a friend’s web album. Instead now I can only upload thru a web browser, 5 at a time.

Are you going to add this functionality to your plugin?


It doesn’t seem that they’ve exposed this to the API yet, but I’ll keep looking. The 5-photo limit you cited was for IE only, and seems to now be fixed, BTW. —Jeffrey

— comment by Peter on November 21st, 2009 at 6:58pm JST (12 years, 6 months ago) comment permalink

Hi Jeffrey, the latest update of the Picasa Web Album exporter does weird things to the Aperture on export. For example, instead of Aperture 3.3 it says Aperture 3.3635857 now (I hope it’s really the plugin and not a new glitch in the Picasa Web Albums).

Regarding your comments on 20091203.100 – the 500 photo limit is only for the FREE version of Picasa Web Albums. As soon as you pay for extra storage, the limit is raised to 1000 photos per album (the other restrictions being 500 albums in the free version and 1000 albums in the paid version; I think this will eventually change now that Google has dropped the storage prices).

Keep up the good work.

Thanks for the clarification on the limits. About the aperture, where exactly are you seeing the problem? The plugin doesn’t touch the image’s embedded metadata, but can refer to it when creating captions if you ask…. —Jeffrey

— comment by Alexander Kunz on December 12th, 2009 at 5:37am JST (12 years, 6 months ago) comment permalink

Thanks for the great plugin. I’m using Lightroom 2.6 and your latest release and having trouble with timestamps. Photos exported through your plugin are marked with the export date, but photos uploaded directly into Picasaweb use the date in the file. Any ideas?

As best I can tell it’s a bug at Google. I’ve just posted version v110 that works around it. —Jeffrey

— comment by Stephen Detwiler on January 4th, 2010 at 11:52am JST (12 years, 5 months ago) comment permalink

Hi Jeffrey, I was wondering how to have the original date & time from when the photo was shot listed in Picasa Web? Right now all the pictures I upload have today’s date (i.e. upload I assume – though it might also be date added to LR catalog).

I can’t imagine you haven’t implemented this, so I’m surely missing something, but I’d appreciate a pointer nonetheless!

Cheers for the great plugin!

Chris from Amsterdam (NL)

As best I can tell it’s a bug at Google. I’ve just posted version v110 that works around it. —Jeffrey

— comment by Chris on January 9th, 2010 at 5:21am JST (12 years, 5 months ago) comment permalink

RFE: It would be nice if I could specify the date for a Picasa album (not the photo but the album) when creating it in Lightroom. Other metadata like location would be nice too, but at least Picasa sets that as unknown. However if no date is specified on the album creation, PIcasa picks the current date. Usually I want the date when the photos in the album were taken.

and the version of LR is 2.6 and the plugin is 20100130.110

Added in v111, but you’ll have to do a manual install if you’re using v110 —Jeffrey

— comment by Elliotte Rusty Harold on January 9th, 2010 at 10:09pm JST (12 years, 5 months ago) comment permalink

Hi Jeff,

I notice that on Picasaweb the Aperture information is incorrect. Often A is close to the
largest aperture of the lens, but not quite. E.g 2.828427, see below
Belichting: 1/160 sec.
Diafragma: 2.828427
Brandpuntsafstand: 100mm
Flitser gebruikt: Ja


Plugin version number is 2091216.107
Lightroom version 2.6 – 632038 – Camera Raw 5.6 – 64 bit
OS: Vista Home Premium / Service Pack 2

Another question:
– Is it possible to display in Picasaweb the name of the lens used next to the name of the camera used?
– Is it possible to display the focus distance?

Kind regards and thank you for the excellent plug-in,

Exif allows for the aperture to be encoded in two ways, one that’s a nice neat number (“2.8”) and another that’s perhaps the more mathematically-accurate value for the specific case (“2.803826”). It allows the same for the shutter speed, which I’ve always taken to be the setting vs. the measured duration. In any case, you can see which Google is choosing to show. You can use my Metadata Wrangler plugin to strip the “Aperture Value” (the non-neat version) on export, and it seems that Google will then fall back to the neat version, “FNumber”.

As for the other Exif metadata, Lightroom doesn’t strip it unless you ask it to (if you ask, it strips almost everything, so if you see the aperture, it’s not being stripped), so it’s up to Google whether they’ll show it. You may want to ask them. If you’re desperate, you could use the template tokens my plugins support to include the info you want as keywords, or in the image caption. —Jeffrey

— comment by Maurice on January 15th, 2010 at 5:44am JST (12 years, 4 months ago) comment permalink

Using your PicasaWeb Export Plugin for Lightroom, I am more or less consistently getting an error message returned from PicasaWeb: Error: 10 STORAGE_UNAVAIL during export. It will happen at varying times, and each time I retry the export several more images (anywhere from 1 to 15) will be uploaded before the error is thrown again. I currently have over 460MB of available space on PicasaWeb.

Running v20100130.110 on Lightroom v2.4, Windows 7.

D’Arcy (Canada)

It’s a Google bug. Strikes all uploaders randomly, it seems. I think it’s related to their servers having issues with the back-end storage, but I don’t know. Nothing I can do, sorry. —Jeffrey

— comment by D'Arcy on February 4th, 2010 at 8:27pm JST (12 years, 4 months ago) comment permalink

How about adding a configurable retry count to handle Error: 10 STORAGE_UNAVAIL (perhaps defaulting to 5 and respecting Google’s API guidelines of course)? That would take care of much of the pain…

— comment by D'Arcy on February 5th, 2010 at 12:17am JST (12 years, 4 months ago) comment permalink

Hi Jeffrey,
I’ve been trying to upload photos to both Facebook (using and and I get the message “An internal error has occured: AgExportSession.photoExportSequence is obsolete; use photoIDExportSequence instead”. I saw another post on this last October and you said it’s an internal LR problem – did you get anywhere with them on this? Really hope it’ll be rectified when LR3 is released! Thanks!

Yikes, my bad, sorry… didn’t test a LR2 change on LR3b. Just pushed fixes for both. —Jeffrey

— comment by Cat on February 10th, 2010 at 7:22am JST (12 years, 4 months ago) comment permalink

OS Windows XP SP3
Lightroom 2.6
PicasaWeb 20100315.116

An error occurred while reading the schema for the plug-in “PicassaWeb.” The plug-in will be disabled.

(This is the message I get when I try to install your plug-in.)

Sounds like your install didn’t go properly… maybe try downloading/unzipping again? If that doesn’t work, email to me the diagnostics from the lower-left section of the plugin manager, and I’ll take a look. —Jeffrey

— comment by Marvin Israel on March 22nd, 2010 at 8:46am JST (12 years, 2 months ago) comment permalink

Hello, I’ve been using your plugins specially the PicasaWeb one (I used the Flickr but switched to picasa) I have a (small) request, is it possible that we can use our own short URL? maybe have an option to input the URL of our shortening service? there are a bunch of them out there but I personally run my own just for security (I guess) my shortener uses a similr API to and it will return a text with the short url…

maybe you could have something like:
shortening service: (text input to enter url) in my case
variable: (text input to enter variable) in my case ?longurl=

this will allow anyone to use any shortening service out there.

let me know is this is possible, this is the only feature I think your plug in misses other than that this is THE plug in for lightroom export

— comment by Shanti on March 22nd, 2010 at 4:31pm JST (12 years, 2 months ago) comment permalink

Just downloaded
Thanks ever so much!
One problem: I am in the UK, and when I try to order prints from my uploaded photos in Picasa, I only get USA companies as options. I presume that the plugin somewhere must say I am in the USA. Is there a way to change this so that Picasa knows I am in the UK, and will therefore offer me the option to order prints from UK companies such as Photobox?
Many thanks in advance,

The plugin doesn’t say anything one way or the other about where you are… I would think this would be part of your Google Account settings. Maybe they don’t offer print service in the UK? —Jeffrey

— comment by Chris Russell-Jones on April 4th, 2010 at 10:13am JST (12 years, 2 months ago) comment permalink

Thanks for the plugin it’s great. I have been a registered user for a while and am very happy. One question, is there a way to upload images to a shared album that I have permission to upload to but do not own? Picasa Web Export Plugin for Lightroom, Version 20100323.117

Thanks again,

Oh, drat, I was working on adding that and got waylayed by LR3 preparation. I’ll try to get to it soon, sorry. —Jeffrey

— comment by Monti Vandiver on April 15th, 2010 at 8:50am JST (12 years, 1 month ago) comment permalink

I am just new to PicassaWeb and am loving your plugin….really a time saver.

I want to have two gmail accounts…one for family and one for fine(r) pix. Can I save the plugin as a preset…one with one gmail signin and one with the other?

I tried it on LR3B2 and it seemed a bit flacky….the gmail accounts would kind of randomly rotate….but not in sync with the preset pushed.

It should work with the presets. Perhaps enable extra debugging (in the plugin manager) and try uploading one photo to each, then send the plugin log (via the button in the plugin manager)….—Jeffrey


— comment by John on April 22nd, 2010 at 5:26am JST (12 years, 1 month ago) comment permalink

Your code is fine…user error on my part….sorry…John

— comment by John on April 23rd, 2010 at 12:31am JST (12 years, 1 month ago) comment permalink

Thank you for such wonderful plugins. I think you’ve saved me about 3 hours worth of work trying to do the same thing with Dreamweaver and Flash (making slideshows for bunches of photos). 🙂
My version numbers: WinXP SP3, LR 2.7 (666138)
Facebook plugin: 20100323.117
PicasaWeb plugin: 20100323.117

I’ve tried several things, but have now resorted to commenting here.

My situation:
It doesn’t matter which plugin I try installing first, but when attempting to install the second plugin in it get this error:
“An error occurred while reading the schema for the plug-in ” Facebook”. The plug-in
will be disabled.”

I’ve resorted to installing one of them and if I need to use the other, I first remove the first plugin and install the other.

Again, thank you very much for such wonderful plugins.

That error is from Lr telling you that the plugin files are incomplete or missing or corrupt. Are you sure you’re not unzipping them over each other, or something? Even after installing into the plugin manager, you have to leave them on disk because “installing” is really just telling Lr where they are. —Jeffrey

— comment by JOe on April 23rd, 2010 at 12:54am JST (12 years, 1 month ago) comment permalink

Hi Jeffrey, this is the first time I see your work. I would like to have lightroom plugin for Picasa on Mac OS. I could not find it on your site. The latest version is a ZIP file which is for windows right? Where can I find dmg plugin?

Hannah yun

The zip is good on Mac and Windows. —Jeffrey

— comment by Hannah Yun on April 26th, 2010 at 9:01am JST (12 years, 1 month ago) comment permalink

I have been using your plug in with registred code. Now it does not show in my export plug in manager anymore. Should I down load and install your plug in again ?.

If it suddenly disappeared from the plugin manager, it’s either because you moved (or deleted) it from where it was when you told the plugin manager about it, or because your Lr preferences have gone corrupt. If it’s still on disk where you put it, it’s likely the latter. )-: You can try reinstalling it if you can find it, or downloading and installing, but if it doesn’t “stick” across a Lightroom restart, you’ll have to blast your preferences file and let Lr build a new one when it starts. —Jeffrey

— comment by Brian on May 20th, 2010 at 7:19pm JST (12 years ago) comment permalink

Thanks Jeff- You are great. With a little donation but got a lot of nice service. I was successful restore your plug
Thanks again

— comment by Brian on May 24th, 2010 at 7:30am JST (12 years ago) comment permalink

Get the following error trying to export to Picasa:System returned “securityError” when Lightroom attempted to use the Internet: Are you sure that your system date and time are correct? System Date and time appear to be correct. Saw a fix for SmugMub, but that did not work for me.. Any help is appreciated.

Everything I know about “security error” errors is in this FAQ entry (which I just created, so it’s not your fault for not seeing it before asking 😉 ) —Jeffrey

— comment by Stephen Hargreaves on June 6th, 2010 at 1:00am JST (12 years ago) comment permalink

Hi and thanks again for this great Plugin.

I’m using 20100510 with LR3…

Yikes, I didn’t think that would even run in Lr3. Its publish is not ready… I’m scrambling to get a version out for Lr3. (I elided the rest of your comment, since everything to do with this plugin on Lr3 will change when I push out the new version, hopefully soon. Status is here —Jeffrey

— comment by Mathes on June 10th, 2010 at 9:38pm JST (12 years ago) comment permalink

Hi there,

Just upgraded to the full version of LR3.
I have installed the Picasa plugin and donated, but there was nowhere to add the registration code… I guess I’m too early for the new version!? Or is there something I missed.

Thanks, and by the way, great plugin, I used it in my Beta install of LR3.


It’s in beta, here —Jeffry

— comment by Seth on June 17th, 2010 at 11:22pm JST (11 years, 11 months ago) comment permalink

Thanks a lot for the great work.
I had the same comment as Seth: it looks like I’m missing something. Do you mean that the plugin is in Beta version or you’re referring to LR3 beta? If former, when are you expecting to release the Picasaweb plugin?
Thanks again,

The plugin for the real Lr3.0 are in beta here. These beta plugins do not work on the Lr3 betas, only the real Lr3.0 or Lr2. —Jeffrey

— comment by AK on June 25th, 2010 at 8:23am JST (11 years, 11 months ago) comment permalink

I am running LR3, never ran the beta. I previously had version 20100323.117 installed and running, but when I upgraded to 20100702.128 and enabled it, I found that I cannot remove the prior plug-in through Plug-in Manager. I went to the modules file and manually removed the plug-in, but it did not disappear from the Manager. Also, the new PicasaWeb is listed as now listed as “jf PicasaWeb”. How do I resolve this?

Lightroom doesn’t let you remove a plugin via the plugin manager if it’s installed in the folder that was the standard-install location for Lr1, so in that case you have to go to disk to physically remove the plugin folder. (You suggested that you did, but you probably removed a different copy.) I pretended “jf” to all my plugin titles because Adobe apparently doesn’t mind naming its Flickr plugin “Flickr”, even though I had one named “Flickr” for years, so seeing the writing on the wall, I changed the name of all my plugins. —Jeffrey

— comment by Randy Black on July 6th, 2010 at 12:59am JST (11 years, 11 months ago) comment permalink

I think it is important to have a way to create a new album from LR3. Why?

It is very convenient to prepare a collection to publish on-the-road. I often do that during my vacation or on the train. But if you do not have created the album on Picasa Web first you are stuck.

So I’ll be very happy to be able to create a new album (or published collection) when disconnected and populate it. The first publish will create the album on Picasa Web if it does not exist and publish all the pictures. How does that sound?


— comment by Pascal Obry on July 10th, 2010 at 2:26am JST (11 years, 11 months ago) comment permalink

Thanks for all your hard work in updating those plug-ins Jeffrey – I’m a big fan of your product and I tell everyone who has interests in how publishing photos to Picasa and Facebook. (-; So I updated to LR3 few days ago, and just donated for the new version of this plug-in (BTW your plug-in has been working so well with my LR2.)

I was wondering, compared to the LR2 version, is there new stuff added to the LR3 version? Not expecting anything since your plug-in works great for my need, but just want to be sure. Also when I installed LR3 it picked up the LR2 plug-ins, as expected not working but do I just delete them off plug-in manager and install as new or?

Additionally, I have export presets in my LR (LR3 picked them from LR2 I guess,) if I upgrade to LR3 compatible version do I lose my presets? I have many presets so I’d like to avoid losing them as much as possible.

Again, thanks for your great product, and hanging there in Japan.

Nothing should be lost with the new versions, in Lr2 or Lr3, but in Lr3 you get support for Publish. Thanks for your kind words, but watch out for terms like “product”, which implies a business and related expectations. The plugins are free and are just a hobby, so best to call them “plugins” 😉 —Jeffrey

— comment by Baiz Yeh - Tokyo Japan on July 14th, 2010 at 7:41pm JST (11 years, 10 months ago) comment permalink

Hi, Jeffrey! I’m Paul and I’m from Poland. First, I have to tell that I’m a huge fan of your woirk – especially this plugin.

However, there is one thing, that IMHO should be implemented. Creating new Album directly from Lightroom 3. Is there any possibility that you could add this feature? If there is, when you are planning to do that?

Yes, it’s on the todo list, but I’d like to let things settle down a bit. I worked on this for 6+ months before releasing it, and need a bit of time to recover, and to address the many issues that have already been reported. —Jeffrey

— comment by Paul on July 15th, 2010 at 11:22pm JST (11 years, 10 months ago) comment permalink

Hi Jeffery, after I upgraded my LR3 from Beta version, I reinstalled facebook plugin from your side. However, I do not know where i can get authorisation code after I have granted to access at Facebook. Can you help?


After authenticating at Facebook and granting the plugin access, Facebook should redirect you to a page on my site that clearly gives you the long authorization code that you then cut-n-paste into the plugin dialog. Occasionally Facebook has issues and they don’t do the redirect correctly, but from what I’ve heard, if you log out of Facebook then log back in and try authenticating from Lightroom, it should work. —Jeffrey

— comment by Hannah Yun on July 19th, 2010 at 9:56pm JST (11 years, 10 months ago) comment permalink

I am on a Mac OSX 10.5.8 and using LR2 – and have just upgraded the Picasa Web Plugin to Version 20100715.131 – and I’m having the same problem as with the previous version (which worked fine for a long time) – I keep getting “the login attempt failed” – and so unable to use the plugin.
I’m a registered user – help!

It could be that Google is having temporary issues, but if it’s still happening, send a log after a failed attempt, and I’ll take a look…. —Jeffrey

— comment by Susan on July 22nd, 2010 at 9:26am JST (11 years, 10 months ago) comment permalink

Feature request: store passwords securely (e.g., in the keychain) or provide an option to not store them at all or to “forget” them. It looks like they’re being stored in preset files right now, obfuscated perhaps, but still…

Otherwise, great plugin, and I sent you a donation!

-Greg (Santa Barbara, CA)

picasaweb-20100715.131, Lightroom 3, Mac OS X 10.6.4

If you log out and edit the credential list to remove them, they won’t be stored anywhere. Lr3 now has provisions for secure password storage built in (it uses Keychain on OSX), so if I can get a million other things off the todo list, I can make use of it…. —Jeffrey

— comment by Greg on July 26th, 2010 at 12:49am JST (11 years, 10 months ago) comment permalink

When I attempt to re-publish modified photos, I’m getting an error that reads “Invalid JSON data in reply from PicasaWeb” followed by two “cancelled” message boxes.

I’ve also observed some other bizarre behavior. For example, the “albums in this publishing service” list in the settings no longer shows checks next to some of the albums that I uploaded images into, but those albums still show up on the list of publish collections.

I’m using picasaweb- 20100729.132, Lightroom 3.0, Windows 7 64-bit.

I’ve gotten a few reports of this but have not been able to track it down yet. If you could enable enhanced logging in the Plugin Manager, then after that if you get this error, send a log, I could try to track it down. —Jeffrey

— comment by Erik on August 2nd, 2010 at 7:09am JST (11 years, 10 months ago) comment permalink

I figured out what caused the publishing problems that I reported in my last comment (Invalid JSON data in reply from PicasaWeb). I changed the setting on PicasaWeb for how the URL is displayed. There is a choice between either a unique identifier or user name. If you change this, the plugin doesn’t seem to like it. I’m guessing something is getting cached that is no longer valid.

— comment by Erik on August 2nd, 2010 at 10:21pm JST (11 years, 10 months ago) comment permalink

Picasa plug-in: 20100814.134

I’ve changed my password for Picasa but can’t find a way to update my account info in the plug-in. Do I just need to remove then re-add the plug-in? Sorry if this has been mentioned else where, but I can’t seem to find the answer.



You should be able to log out from the export dialog, then log back in with your new credentials, then dismiss the export dialog, and you should, in theory, be fine. —Jeffrey

— comment by Andy on August 15th, 2010 at 2:27am JST (11 years, 9 months ago) comment permalink

>Dynamical creation of Album on Picasa and Facebook From Exif Parameters<

Hey Jeff,

In LR2, your plugin was able to dynamically create Facebook Albums (I do not know for Picasa) from Exif parameters. I used it with OriginalDateTime to create one album per day. This did not require any manual operation on Facebook.

Now, I used your Facebook and Picasa plugins and I cannot reproduce the automatic procedure. I need to create these albums in each web sites.

Is it possible ? Perhaps in a future release ?

Thanks for your great job, Jeff

You can do it in a normal export, just not (yet) in Publish. —Jeffrey

— comment by Alain RACINE on August 16th, 2010 at 3:15am JST (11 years, 9 months ago) comment permalink


a suggestion: it would be very handy if we could use the templates in the watermarks, too. This way we could stamp all sorts of exciting stuff on the images (time, place, copyright, meta data, etc.) with such an ease.

Thanks for considering it.


Unfortunately, Lightroom doesn’t give the plugins any access to the watermarking features, so what’s there is there. —Jeffrey

— comment by Josh on August 31st, 2010 at 4:06am JST (11 years, 9 months ago) comment permalink

Hi Jeffrey and a big thank you for the picasaweb plugin – a wonderful contribution to making it simple to publish photos for my family/friends. Everything works fine, just done my first export but I have a question based on my base ignorance, low intelligence and general all round stupidity:

When I export from Picasa to Picasweb, I’ve always picked the resolution setting ‘1600 pixels for prints, screensavers and sharing’. I would like to use this setting when I export using the Picasweb plugin for Lightroom but don’t have a clue how to do so because it speaks the language of ‘quality’ 0-100%, ‘limit file size’ in K, image sizing (currently set at W640, H640 and resolution (currently set at 240 pixels per inch).

How do I make any of that bewildering array of settings add up to ‘1600 pixels for prints, screensavers and sharing’?

Try format=JPEG, quality=75, color space = sRGB,, resize to fit long edge = 1600 —Jeffrey

— comment by Phil Wolsey on September 1st, 2010 at 7:24pm JST (11 years, 9 months ago) comment permalink

‘Try format=JPEG, quality=75, color space = sRGB,, resize to fit long edge = 1600 —Jeffrey’

That works, and I’ve learnt something! Thanks a million. Phil

— comment by Phil Wolsey on September 1st, 2010 at 9:10pm JST (11 years, 9 months ago) comment permalink

Hey J,
First of all, thanks for your work on this plug in – it’s great!
However, I’m having some problems currently.
I have set up a publishing service a little while ago, but has since stopped using it. I even deleted it at one point, and have just been exporting pictures regularly to my picassa.
Yesterday i have made some changes to my picasa account (transferred some pictures from one album to another, renamed one album and deleted another).
Today i wanted to set up the publishing service again. I read through your instructions, and have figured i should “Refresh all remote URLs” just to be safe. However, i am getting the following error:
“invalid json data in reply from picasaweb” whenever i do that.
any ideas?
I am using Lightroom 3.2 and plugin version 20100829.136, on Windows 7 64.

I just pushed a new version of the plugin… please give it a try, and if it doesn’t fix it, please send a log. —Jeffrey

— comment by Oded on September 8th, 2010 at 5:09pm JST (11 years, 9 months ago) comment permalink

Hi Jeffrey,

I recently ungraded from LR2 to LR3 and I downloaded the latest plug-in (export to Picasa Web) as of today (Sept. 9, 2010). Although I had given a donation on November 19, 2009, it seems to not know it and I’m still on a trial version. Maybe all is normal but I’d like an explanation please. Thank you, I love your plug-ins.


Please see this FAQ —Jeffrey

— comment by Jean-Claude Babin on September 10th, 2010 at 4:16am JST (11 years, 9 months ago) comment permalink

Does this plugin support creating a new album? I’ve searched around but I was not able to find any information on creating a new album from the plugin.

The only way I’ve been able to create a new album is to go into picasaweb, create it, and then go into the lightroom and create a publish service using the new album.

You can create one from the Export dialog; I hope to add to the Publish dialog soon. —Jeffrey

— comment by Thang on September 10th, 2010 at 10:08am JST (11 years, 9 months ago) comment permalink

Hi Jeffrey, I am using the latest picasa plugin with lightroom 3.2. I noticed that many of Picasa albums images were not downloaded into the appropriate lightrooms picasa folders, but many were. Why is that happening, and what can I do to solve this issue.

I don’t understand what you mean by “were not downloaded”, but if you’re referring to the “associate images already at PicasaWeb” feature, it’s very hit and miss, sorry. —Jeffrey

— comment by norbert on October 25th, 2010 at 3:06am JST (11 years, 7 months ago) comment permalink


Have you had users of your Picasa export plug-in complain that your plug-in corrupted their account with Picasa Web? I am 99% sure your plug-in created a problem with my Picasa account. After uploaded this picture – my account was messed up … I can no longer do thinks like modify captions, use any option in the EDIT drop down on a specific page, add a comment (I get an error message when I try).

Any feedback you have is appreciated. I have years with of pictures and a messed up account and I cannot find a way to contact Google to help.

Thank you!

A third-party app like my plugin shouldn’t be able to cause that kind of havoc, so if it does, it’d be a bug with Google, but frankly, I can’t imagine how this might transpire. —Jeffrey

— comment by Brandon Atkinson on November 20th, 2010 at 9:52am JST (11 years, 6 months ago) comment permalink

Bonjour et merci pour votre excellent plugin.
Il est possible de marquer manuellement une photo comme devant être republiée (même si elle n’a pas subi de modification depuis sa dernière publication). Et c’est parfois utile.
D’autre part, les photos ayant subi des modifications depuis leur dernière publication sont rangées automatiquement dans la categorie des photos à republier. Mais parfois ces modifications sont mineures (comme l’ajout ou la suppression de mots-clefs sans modification de la photo en elle-même) et la republication n’est pas indispensable. Est-il possible, manuellement, de retirer ces photo de cette categorie sans devoir les republier ? Cela me serait utile egalement.
Vous remerciant. Cordialement.

That would be nice, but Lightroom currently doesn’t allow for it. )-: —Jeffrey

— comment by Hervé Chalamet on December 25th, 2010 at 12:32am JST (11 years, 5 months ago) comment permalink

– PicasaWeb Export V. 20101217.143
– Mac OS 10.6.5
– Lightroom 2.7

Your plugin use to work like a charm but now I get this error message:

“PicasaWeb 404: attempt to index a nil value”

I can’t upload to Picasa any more 🙁

I think I’ve fixed this in 20110113.144 —Jeffrey

— comment by Thomas on December 29th, 2010 at 1:54am JST (11 years, 5 months ago) comment permalink

Hi! First, thanks for making this plug-in.
I am considering moving from Picasa to LR and I am impressed by the LR 3 trial. I publish most of my photos through Picasa web albums and that’s how I found your site. Picasa support is what has me on the fence about purchasing LR. I tried to set up your plugin but it doesn’t seem to be working. Do you know if there’s away I could try it with the trial version of LR3?


The plugin should work just fine while Lr3 is in trial mode. You can’t register the plugin until you own Lr3, but the plugin trial mode is longer than the Lr3 trial mode, so that shouldn’t be any problem. —Jeffrey

— comment by Sherwin on December 30th, 2010 at 2:24pm JST (11 years, 5 months ago) comment permalink

I tried to use your picasaweb plugin .But how do you create a NEW album directly from Lightroom (without choosing one existing already)

Thank your for your help


See the “Tools” section of the Export Dialog. —Jeffrey

— comment by Toropoff Vadim on December 31st, 2010 at 3:02am JST (11 years, 5 months ago) comment permalink

Hi Sherwin – I also had problems getting this plug-in to work for Picasa. It was one of the factors that made me move five years of pictures from Picasa to Flickr. If you are serious enough about Photography to use Lightroom, I think you will really enjoy Flickr. And lightroom 3 comes with a plug-in out of the box which allows you to upload to it. Best of luck, Brandon

— comment by Brandon on January 7th, 2011 at 10:07pm JST (11 years, 5 months ago) comment permalink

Hi Jeffrey,

do you think it would be possible to FIRST delete the images to be deleted THEN upload changed images and THEN the new images?

I am asking because Picasa has a limit of 1000 images per album, and currently I’m stuck as it always tries to upload new images before deleting the old ones, which of course fails.

Kind regards,

The order is decided by Lightroom, not the plugin, so there’s little I can do. I think it’s a bug that they don’t let you invoke the deletions via alt-Publish the way they let you do selective Publish, and I’ve submitted the bug, but no word on whether Adobe even agrees that it’s a bug. —Jeffrey

— comment by Uwe on January 11th, 2011 at 6:00am JST (11 years, 5 months ago) comment permalink

Uhh, I feared as much. Thanks for your reply & effort, Jeffrey. I didn’t even know about the selective publishing option, thanks for the hint – it’s good to know even though it doesn’t help in the current situation.

— comment by Uwe on January 13th, 2011 at 5:53pm JST (11 years, 4 months ago) comment permalink

Hi Jeffrey

I recently changed my google account password and this seems to have affected my ability to export to my picasaweb albums.

I cannot seem to to be able to do anything as all I can see is the phase – Oops, not properly authenticated, please log in from the export dialog box etc.

I can’t seem to figure this one out? Each time I try to log in I receive – Capture required, or – Bad authentication.

If I try to create another publishing service through your plugin, my picasa log in details aren’t recognised.

Any help with this matter would be appreciated.

Kind Regards

Brett Holland

I’m not sure when Google started requiring captcha on some accounts, but it seems new. Until I can update the plugin to handle it, the best I can suggest is to log out from within the plugin, then login from a browser. Hopefully that’ll reset the “needs captcha” flag, and then you can re-login from the plugin. —Jeffrey

— comment by Brett Holland on March 7th, 2011 at 4:23am JST (11 years, 3 months ago) comment permalink

Hello Jeffry,

i resently chanced to windows 7 64bit with 64bits Lightroom 3
Now i got the following error message each time i try to export lo Picasa:

Could’nt render image: readNegative: dng_error_directory_not_found

and then it is canceled.

Before i never had problems did i do soething wrong

Best regards


It looks like Lightroom can’t find the folder where the master image negatives are… do you have a disk offline, or did you shuffle around drive letters when changing your OS? Find the folder in Library, and you’ll probably find that it has a “?” icon… right click and “find folder” to tell Lightroom where it is now. —Jeffrey

— comment by werners on April 17th, 2011 at 5:10pm JST (11 years, 1 month ago) comment permalink

Hello there – I’m using version 20110419.152, and I’ve discovered following problem with keywords.

I’m using LR3’s publish service. I would like photo to be uploaded to Picasa and tagged with some of the keywords this photo has in LR. Even though I’ve installed keyword wrangler, it looks like I can choose between following options:

– ‘Do not explicitly send keywords from Lightroom catalog’ checked + filtering in keyword wrangler = proper set of keywords in exif of the photo, but no “tags” in PicasaWeb (right-hand column on single photo view page).
– ‘Do not explicitly send keywords from Lightroom catalog’ unchecked = exif has proper set of keywords (filtered), PicasaWeb tags consists of all keywords (not filtered).

This sounds like a bug, right?

I’m not familiar with “keyword wrangler” (do you have a link?), but I’m sure my plugin isn’t working with it… it’s likely updating the image file, but the plugin is referring directly to the Lightroom catalog. —Jeffrey

— comment by yacoob on May 1st, 2011 at 8:47am JST (11 years ago) comment permalink

I love your picassa plug-in, and I appreciate your efforts to evolve and improve it. It’s been wonderful to see it improve. That said, it drives me crazy that you release new versions of it every 3 days, and I can never actually use the plug in without downloading a new one. The benefits and time saving of the plug-ins are negated by the extra effort of constantly updating the plug-ins themselves. Just a thought… ever considered of releasing updates less frequently, such as every 2 months or so.

Wow, talk about something from the “can’t please everyone” file. Just ignore the updates if you don’t want to deal with them. If your “can never use the plugin without downloading a new one” stems from some sort of OCD, you’ll have to find a way to cope yourself. —Jeffrey

— comment by Steve Wagner on May 7th, 2011 at 3:06pm JST (11 years ago) comment permalink

MacOS 10.6.7
LR 3.4.1
Picasa Web 20110606.155

Hi, love the plug in, always worked brilliantly, however when I try to export now, I get a very strange error message “Retrying after mysterious Google error ‘STORAGE_UNAVAIL’ error,”

At this point I need to cancel to prevent continuous retries. Also, the first picture from a sequence of pictures are actually uploaded, but only the first, multiple times.

Apologies if you already have received this post, I was not sure if it had sent.

No one knows why Google issues this error. All uploaders seem to see it at times. Only thing to do is wait and hope. —Jeffrey

— comment by Michael Avis on June 13th, 2011 at 9:43pm JST (10 years, 11 months ago) comment permalink

MacOS 10.6.7
LR 3.4.1
Picasa Web 20110606.155

OK, I’ll do that. One thing that also happens that I forgot to mention is that after trying to do an export and aborting it (due to that error message and only the first picture getting uploaded multiple times) when I go into the LR plug-in manager, jf PicasaWeb is shown with a yellow icon and the status is “installed; may not work”.

To remedy this I remove the plug-in and install it again – but when I try it again, I get the exact same outcome with the Google error and the plug-in going back to the “installed; may not work” status.

The “installed; may not work” is Lightroom reflecting the fact that the plugin reported an error. It’s unfortunate because the plugin is just passing along what Google returned. It’ll work fine, but you can clear the warning if it bothers you by reloading the plugin, in the middle section of the plugin manager. —Jeffrey

— comment by Michael Avis on June 14th, 2011 at 12:35am JST (10 years, 11 months ago) comment permalink

MacOS 10.6.7
LR 3.4.1
Picasa Web 20110606.155

Just about to upgrade to 20010613.156 but wanted to say that the mysterious Google error has gone away, just exported no problem. I had changed nothing my end, the plug-in is innocent!

— comment by Michael Avis on June 22nd, 2011 at 11:01pm JST (10 years, 11 months ago) comment permalink

Hi Jeffrey! If I’ve updated a gallery name in PicasaWeb (through the web interface), how do I get that updated name to show up in the jf PicasaWeb collection in Lightroom?

Use the “refresh list” button next to the list of albums. —Jeffrey

— comment by Raoul on June 28th, 2011 at 7:31pm JST (10 years, 11 months ago) comment permalink

> Use the “refresh list” button next to the list of albums. —Jeffrey

I did that several times, and I did it just now as well. The proper names appear in the Edit Settings dialog box, but they don’t update in the Publish Services collection. And I can’t change them there, either. When I double click on a gallery name, a dialog box for changing its name comes up, but the field is grayed out.

Oops, sorry, I read your original question wrong. It’s not possible to change the name of a gallery (due to bugs in Lightroom), so the best I can suggest is to delete it and re-add it, using the “populate” feature to refill it without having to reupload anything. —Jeffrey

— comment by Raoul on June 28th, 2011 at 8:37pm JST (10 years, 11 months ago) comment permalink

I can’t install your plugin. I get this error from Lightroom:
BASE:69: attempt to call ‘?’ (a nil value)

Plugin Version: 20110712.163
Lightroom Version: 3.4.1
OS: Windows 7 Home Premium 64-Bit

Thanks for your help!
I’ve seen this a few times and never understood it, but it seems that if you restart Lightroom a few times, it tends to go away. If not, try installing from a fresh download. —Jeffrey

— comment by Sander on July 22nd, 2011 at 11:26pm JST (10 years, 10 months ago) comment permalink

Can you make your program run multiple processes in the future? I am sure that uploading is not a CPU intensive task so while it is doing that it could be processing other photos. Thanks

It should be able to handle multiple simultaneous uploads, though there’s a bug in Lightroom such that they might occasionally kill each other. —Jeffrey

— comment by KieranMullen on August 3rd, 2011 at 3:41am JST (10 years, 10 months ago) comment permalink

I have seen the upgrade for the PicasaWeb plugin version 20110821.167 and gave it a try. I’ve read about the auth changes and that I’d need to re-auth. But what happened instead that it didn’t work at all. It said I canot re-auth and should do it in some export dialogue, no idea what that’s got to do with the publish dialogue. Then came some more debug assertions, invalid URL messages and I was back. In the whole process, my album name was there twice, with all the photos in one of them. I have now downgraded to 20110712.163 again and could delete the duplicate album with no data loss as it seems. Maybe that auth change wasn’t all that good? Or is it incomplete yet?

When the popup says “Note: please visit the Export Dialog to do this, even if you have Publish Services“, it’s for a reason. Publish doesn’t contain any mechanism to change logins or login/logout, and the export dialog does. Nothing will work with the new plugin until you reauthenticate. If you upgrade then downgrade, I don’t even want to think what will happen to your catalog state. Better, instead, to just follow the instructions.—Jeffrey

— comment by Yves on August 21st, 2011 at 7:20pm JST (10 years, 9 months ago) comment permalink

I just upgraded to 20110821.167 and is warned to reauthenticate at the top of the Export Dialogue. Where exactly is that dialogue box?

The Export Dialog is the dialog that shows up when you click the “Export” button. —Jeffrey

— comment by Lars Olesen on August 30th, 2011 at 4:23pm JST (10 years, 9 months ago) comment permalink

Good night:

In April I made a small donation to record plugging in my software picasa lighroom 3. Due to computer problems I had to reinstall the software on 2 occasions so now the registration code is invalid.

Can you help with this problem?

Thanks for your work and attention.


Your code is still valid for the picasaweb plugin for the Lr serial you first installed it on. If you need a code for a different plugin, or if you’ve changed your Lr serial, you can always generate new codes (with 1-cent transactions, if you like). —Jeffrey

— comment by Elena on September 5th, 2011 at 4:20am JST (10 years, 9 months ago) comment permalink

Hi, i have a problem with your Picasaweb-Plugin.
I use the latest LR (3.4 ithink) and your latest plugin, i downloaded it nce agin right now. When i wonkt to export videos (mov) to picasaweb the export is stopped after a view minutes an an error message accours: “Attempt 1 (Error Connection Lost …).

Can you help me? The other functions are running well and also i can uplad a video to picasaweb “by hand”

Thanks in advance!


It sounds like the video is taking too long to upload, and your connection to Google is timing out somewhere along the line. Unfortunately, I don’t think there’s much I can do but to suggest more bandwidth… )-: —Jeffrey

— comment by Markus on September 6th, 2011 at 11:38pm JST (10 years, 9 months ago) comment permalink

Hi Jeffrey,

Great product. I just found a small bug.
I have my tags grouped under several parents (and greatparents).
These parents are also mentioned as single tags in Picasa while they are not having a checkmark.
Is there a way to suppress the parents during the export?


You can mark each keywords as “Include on export”, or not, via the keyword’s context menu in the keyword list in Library. —Jeffrey

— comment by Hans on September 11th, 2011 at 7:25am JST (10 years, 9 months ago) comment permalink

I’ve been using your plugins for a while now, but not since google started “merging” picasa and google+ photos.
Using version 20110908.169 of Picasaweb
Lightroom 3.4.1 on a 2010 iMac running OS X Lion

I’ve been able to authenticate to my picasa account.
When I try either to straight export pictures to PIcasa, or to use the Picasa publish service, the process will randomly stop with an error 400, 404 or 500. Sometimes it will have uploaded pictures, sometimes not.
I’ve also tried relinking pictures that are both on Picasa and in LIghtroom. Again, it works for one but not the other ….

I’ve tried variations in sizes (from 15 to 2 Meg) but it doesn’t seem to change anything.

Also, as a control, I have NO problem using the Picasa uploader from the site on exported jpg)

I’m probably missing something basic, but for the life of me i can’t figure out what. Would you have a clue ?

All I can guess at this point is flakiness at Google. It’s likely that their uploader uses different endpoints than my plugin, so I can understand one working but not the other. I’ve found bug reports by others of these kind of errors dating back to 2009, but no one has been able to pin them down. I’m not sure there’s much I can suggest but keeping your fingers crossed. —Jeffrey

— comment by Paul A. on September 14th, 2011 at 3:35am JST (10 years, 8 months ago) comment permalink

I just registered the jf PicassaWeb plugin, and now it doesn’t work. I get a message:

“Warning: This version of the PicasaWeb plugin uses a new Google authentication API, so prior authentications no longer work. Please visit the Export Dialog re-authenticate. Note: please visit the Export Dialog to do this, even if you have Publish Services; after reauthenticating, you can dismiss the Export Dialog.”

Unfortunately, I do not know how to find Export Dialog, so I am not able to re-authenticate. Please help me because I’m stuck.

Thank you,

The export dialog is the one that pops up when you press the big “Export” button in the lower left of Library. —Jeffrey

— comment by Michael Green on October 10th, 2011 at 11:26am JST (10 years, 8 months ago) comment permalink

First of all, let me say thank you. This plugin does so much more than I expected! I was thrilled at the ability to associate existing images in lightroom with those in picasa web albums. Unfortunately I seem to have run into a little problem. So I migrated from Picasa to Lightroom and in the process of doing that I also imported all of the original versions in the Originals and .picasaoriginals directories. This means that for images that I edited in Picasa I have two versions with the same name. It seems that the plugin will not attempt to associate images when there is more than 1 with the same file name in Lightroom. Just wondering if you can suggest any workarounds.

The whole “Associate” stuff is a big can of kludgy worms… the best I can suggest is to either associate them manually (which would be arduous if there are many), or to remove the .picasaoriginals images from your catalog, do the association step and hope for better luck, then add the picasaoriginals back. Not very elegant, sorry. —Jeffrey

— comment by Paul on October 14th, 2011 at 4:03pm JST (10 years, 7 months ago) comment permalink

I use lightroom and picasa web album. I get many help from this plugin. thanks.

— comment by Choi byungjun on October 17th, 2011 at 1:20am JST (10 years, 7 months ago) comment permalink


Great plug-in! I had a question about upload quality.

I went for 100% (despite the warnings) on the basis that I want those who get my webalbums to be able to download and print them in high quality prints.

So two questions.

1. I noticed that when I uploaded the same pics via Picasa itself, the file size in webalbums is slightly smaller, even though I uploaded those at “original size (slowest upload)”. Not sure why this should be. Do you know?

2. Is there REALLY no benefit in uploading at 100% quality? If I those I share my pics with to be able to do high quality prints (indeed, to some extent I use webalbums as one of a number of backups, another reason to keep them high quality), then how low below 100% can I go: 90%, 80%, or … ?

Sorry about my naive questions.


When you say “the same pics”, do you mean that you first export with Lightroom, having the plugin save the exported copies locally as well, then you uploaded those locally-saved copies via other means, and the result is different? That would be strange. But if you’re comparing uploading an original JPG one way, and a Lr-generated JPG via Lightroom, of course they’ll be different. As for the 100% quality issue, in many cases, yes, there is really no benefit whatsoever, but “many cases” doesn’t mean “all cases”, so if you want 100%, go for it. I don’t. See my writeup on JPG quality to better inform yourself, then make your decision. —Jeffrey

— comment by David Bain on November 7th, 2011 at 6:55am JST (10 years, 7 months ago) comment permalink

Hi Jeffrey – I can’t figure out where to input the User ID in the Publishing Manager.

When you say, “Include the account id (in addition to the full name that’s already there) in the Publishing Manager login section, to allow multiple accounts associated with the same real name to be easily differentiated,” does this mean we can input a User ID for a G+ Brand page that we have and upload photos to that, too?

Or should I create a separate PicasaWeb export service specifically to handle my Brand Page, and use the appropriate ID number?

Thank you again for all your hard work on these plugins.

If you want to Publish to different PicasaWeb ids, just create a new publish service and authenticate to the new id. When you “authenticate” it’s to whatever ID you’re logged in with the browser, so make sure you’re on the target ID there before you start the authentication process in Lightroom. —Jeffrey

— comment by Charles Payet on November 19th, 2011 at 11:48am JST (10 years, 6 months ago) comment permalink

Once authenticated can we save this authentication and authenticate to another account and save that one too. I have two Picassa accounts, one account where I store all photos with no download capabilities and one restricted account with download capabilities. It would be appreciated not to have to re-authenticate everytime I change accounts. Is this possible?

Sure, after having authenticated to the second account, when you next deauthenticate a popup menu button appears with the accounts for which you already have authentication, and you need just select one. —Jeffrey

— comment by Real Mayer on November 26th, 2011 at 7:02am JST (10 years, 6 months ago) comment permalink


Very nice plugin. I do miss the possibility to specify the size and quality of pictures per album when using the publishing service as any updated picture will get the most recent size picture uploaded if I understand things correctly.

Using version 20111012.173 of “Export to PicasaWeb” on Lightroom 3.5 [775451].

Best regards
/ David
You can always use a normal Export for one-off uploads… Publish is intended for an ongoing relationship, and in that school of thought you’re not going to be changing the size from day to day. —Jeffrey

— comment by David on November 28th, 2011 at 1:26am JST (10 years, 6 months ago) comment permalink

Hi Jeffrey and thanks you for your work!
I set up “Export to PicasaWeb” Lightroom Plugin without any other your plugins but I do not see “Snapshots on Export” section in it. Where could be the problem?

Using version 20111012.173 of “Export to PicasaWeb”, Lightroom version: 3.5 [775451], Operating system: Windows 7.

WBR, Dmitry

That section is included only in a normal export, not in Publish. It doesn’t feel like it makes much sense in Publish….. do you think it should be there, too? —Jeffrey

— comment by Dmitry Bulgakov on December 1st, 2011 at 4:42pm JST (10 years, 6 months ago) comment permalink

Yes, I think it would be useful feature.

I want to ask you about statement written before:
1. In chandelog on version 20100323.117 of “Export to PicasaWeb”: New when running Lr3b2 is a new “Snapshots on Export” section, which is basically a built-in version of this new plugin.
2. In description of “Snapshot on Export”: Note that this functionality is already included in modern versions of my export plugins (…, PicasaWeb, …), so you do not need this plugin when exporting via those plugins.

Is this about feature we discussing or not?

WBR, Dmitry

Yes, “Snapshot on Export” is not needed for any of my “upload to…” plugins because it’s built in. The snapshot-on-export plugin would be useful for other kinds of exports… export to disk, Adobe’s built in plugins, other’s plugins, etc. —Jeffrey

— comment by Dmitry Bulgakov on December 3rd, 2011 at 5:31am JST (10 years, 6 months ago) comment permalink

Jeffrey, I don’t understand 🙂 If “Snapshot on Export” built in “Export to PicasaWeb” then:
1. How can I export to disk using this features (Snapshot on Export) if “Export to PicasaWeb” do export to Goggle Picasa Web only?
2. Where can I see “Snapshots on Export” section if I set up only “Export to PicasaWeb” plugin? I do not see this section in settings of “Export to PicasaWeb”. I do not see this section in settings of standard “Hard Drive” export plugin.
WBR, Dmitry

The stand-alone plugin is for any export, but you have to enable the plugin then add the “Post-Process Action” (see the lower-left corner of the export dialog). It’s already there in the PicasaWeb export, but not in the PicasaWeb Publish, but I think I’ll go ahead an add it in the next version. —Jeffrey

— comment by Dmitry Bulgakov on December 20th, 2011 at 7:52pm JST (10 years, 5 months ago) comment permalink

Thank you for your plug-ins and for the hard work you obviously do to maintain them!

I just updated the Picasa plug-in (20111216.177) and had to do it manually. I’d sure like to optimize things so that I can click the button in the future to update.

I think one of the problems may be that I have 3 different folders for each time I have installed LR – 2.0, 3.5 and 3.6. Do I need to move all the plug-ins to a common folder under adobe/lightroom or do I need to do something different when installing new versions of LR so as to avoid separate folders for each version?

Except for the special system folder that Lightroom used in Lr1, Lightroom doesn’t care where plugins are stored. I’d suggest having one “Lightroom Plugins” folder somewhere, and storing them all there, and sharing that folder (wherever it is) with all your versions of Lightroom. Not sure why you’ve still got Lr2 around when you’ve got Lr3, but it’s fine to have both apps pointing to the same plugins. —Jeffrey

— comment by Nic Showalter on December 22nd, 2011 at 9:42am JST (10 years, 5 months ago) comment permalink

I’m currently using 20111216.177 and see that a newer version is now available but when I try the “upgrade now” button I get the message “The plugin does not seem to be installed in a location where Lightroom can write to it”

I have all my plugins in a common folder in the adobe/lightroom folder – is there something else I need to do to enable that “upgrade” button?



If the plugin can’t write to the parent folder, it can’t do the upgrade. Check your folder permissions, I guess. —Jeffrey

— comment by Nic Showalter on December 22nd, 2011 at 11:34pm JST (10 years, 5 months ago) comment permalink

Ok, but it started to work (new item in Post-Process Action) only after I installed “Snapshot on Export” 🙂
WBR, Dmitry

The built-in one doesn’t show up there… it’s just with the other sections. —Jeffrey

— comment by Dmitry Bulgakov on December 23rd, 2011 at 9:55pm JST (10 years, 5 months ago) comment permalink

Using Picasa Web Version 20111222.178.

Thanks for making this plugin available. I’am hoping you can help me with one problem.

When I upload the my photos from lightroom to Picasa web using your plugin, non of my lightroom edits are uploaded with the photos.

What am I doing wrong. If I export to my hard drive, the photos are exported with all of my lightroom edits?

Am i doing something wrong?

It sounds as if you’re got the format set to “Original” (the original master image) rather than “JPEG”. —Jeffrey

— comment by TateJ on December 27th, 2011 at 5:56am JST (10 years, 5 months ago) comment permalink

First: thank you so much for your hard plugin works. I use your Flick and Facebook ones.
Question: Any future plans for a Google+ lightroom plugin?

Yes, but Google has to release an API, first. —Jeffrey

— comment by gobeco on December 31st, 2011 at 8:43pm JST (10 years, 5 months ago) comment permalink

Hey, thanks for this! It is awesome… with one issue: on a network timeout (I assume between me and picassa) there is a modal dialog telling me about a retry. The cancel button on this doesn’t work and the dialog never goes away. I have to force quit lightroom to continue.

Unfortunately, there’s nothing I can do about that. The cancel button merely leaves a note for the plugin to abort the next chance it gets, but if things are locked up deep within the OS networking code, Lightroom and the plugin never get a chance to act on it. It’s rare that the OS never returns control to Lightroom, but it seems that’s what’s happening in your case. )-: —Jeffrey

— comment by mason bryant on January 3rd, 2012 at 4:09am JST (10 years, 5 months ago) comment permalink

Hi Jeffrey, can you tell me whether there’s a 1,000 or 10,000 photo limit per PicasaWeb gallery? I thought it stood at 10,000, but today, after uploading 1,000 photos to a gallery, I got an error message telling me I’d reached my limit.

I don’t know their limits offhand, but if they’re telling you it’s 1,000 photos, I’d tend to believe them. —Jeffrey

— comment by Raoul Pop on January 9th, 2012 at 1:52am JST (10 years, 5 months ago) comment permalink

Hi Jeffrey, i would transfer from picasa app completely to LR, your plugin is a great help for me. But there are still some minor functions that would come handy. Either i didn’t get everything right from your plugin documentation, or these features are missing 🙂

Mainly my workflow is importing the photos to a dated, and named dir (Windows AutoPlay photo import) and use that as picasa album name. Is this doable with your plugin, or i should create some workaround?

Keep up the good work!

br, Lajos from Hungray

The rename during import is part of the normal Lightroom import, so once you get them into a folder with a name you like, you can use the plugin’s “auto dest” (automatic destination) feature to create the album as Picasa. For an example of the same kind of thing using my Zenfolio plugin, see this writeup, and apply the idea to your needs. —Jeffrey

— comment by Lajos Kelemen on January 11th, 2012 at 6:55pm JST (10 years, 5 months ago) comment permalink

I hate being a snob!!!!

So today I was thinking there HAS to be a better way of uploading to picasa. I hate flickr and detest facebook and this way I can keep my privacy. So off to google I went..I ran across your plugin but somehow it had a date of 2008 attached to it… and the photo looked like it might have been an older version. I thought.. ugh. old sh*t nobody updates anything especially free plugins and they’re ususally bugg as heck. so I kept googling. like half an hour later I saw it listed again and then again and then again. I decided okay let me just follow the links… I log in and the latest update is.. *drumroll* today! I’m like well alright. I download and guess what? my lightroom wasnt up-to-date enough for th plugin

Lesson learned!!!!! hahaha so I had to upgrade lightroom to even use this “old and seemingly forgotten plug in” turns out is isnt old but ESTABLISHED and well used and well supported.

I was happy to donate and I welcome you as the first plug in and likely the most useful thing I’ll have done. Everything uploaded with a cinch, instructions for every single step (naming folders, donating) everything well documented. Definitely the best free anything I’ve used and so impressed I kept checkign to see if it actually worked. I’m so used to things not working lol..

Anyway kudos and I’ve learned to definitely go with the top result on google. You’re number one for a reason!!!

Thank you for the great work, hope people donate so you can continue your excellent work.. If you do one for tumblr I’d pay twice. I also thought the twitter update is cute. I was tempted to test it out but it was a private album so couldnt but soon.. soon.. I will push alllll the buttons lol and I cant wait.
thanks again!

— comment by babyGIrl on January 14th, 2012 at 4:10pm JST (10 years, 4 months ago) comment permalink

Live in NY,writing from Mexico.
To make a new album for Picasa I have to go to edit settings and create the album but then I get a message that there are no photos to upload. I then have to go back to lightroom and drag the photos into the album. Is there, or, can there be a way to create the new album before going into edit settings?
Also, when uploading from Picasa there is the ability to choose the pixel count (1600) or original. I need to upload full resolution sometimes so people can then download for print. Any suggestions?

About the latter thing, you need a separate publish service for separate upload types (e.g. original vs such-and-such a size), but for one-off uploads of any type, it’s probably easier to just use Export rather than Publish. About the new-album-creation workflow, it’s not very smooth, I know. It’s the result of working around layers and layers of bugs in Lr3.0, and now that some have been fixed, I should revisit it, but that’s a lot of work in a fragile area, for relatively little gain, so I’ve been resisting… —Jeffrey

— comment by carl Meisel on January 20th, 2012 at 2:02am JST (10 years, 4 months ago) comment permalink

Very useful plugin for Picasa! Many thanks! Very recommended.

— comment by geminot on January 22nd, 2012 at 4:57pm JST (10 years, 4 months ago) comment permalink

Picasa Limits:

Maximum number of web albums: 10,000
Maximum number of photos and videos per web album: 1,000

Free Storage Limits:

Basically, keep your pics resized to 2048×2048 or less and they won’t count towards your storage limit of 1GB.

— comment by Matt on January 27th, 2012 at 10:01pm JST (10 years, 4 months ago) comment permalink

Jeff….I just updated to latest version….using LR4b, on Win7 64bit.

I had just processed a few images and decided to load to Picasa. Went through the authentication. Then fill out export parameters, successfully (I think) created a new album. Clicked save….it churned for a bit, then LR4 died.

Restarted LR4, it churned for a lo-o-ong time at the logo screen, then longer with an image up, then final started throwing off error messages….if I am correct, it indicated corrupt collections…messages from Jf Picassa. Eventually other error messages, then LR died.

Removed Picassa code from directory. Restarted LR4, which came up clean. Set catalog to backup/cleanup. Closed LR. Put Picassa code back. Restarted….same problem.

Please advise….John

I’ve gotten a few reports like this and have not been able to replicate it myself, but I’m not too worried because there are significant “beta” aspects to this beta (it’s really an incomplete beast under the hood) so I expect the Lr4.0 (or second beta, if there is one) to be much better. —Jeffrey

— comment by John Schwaller on February 6th, 2012 at 9:25am JST (10 years, 4 months ago) comment permalink

There is no way to contact you about other topics. Perhaps you could put that on your website somewhere? Any plans to make an upload to storage cloud option? Such as Amazons S3 or Google’s Developers Cloud Service?

Also how long are you planning on the plugin pages getting with all the posts and software updates on one page? :-p


My email address is on the “About Me” page. I’ve no plans for cloud-storage plugins. Don’t know what to do about the long pages, except that doing nothing is easiest. 🙂 —Jeffrey

— comment by Kieran Mullen on February 23rd, 2012 at 4:43pm JST (10 years, 3 months ago) comment permalink

Perhaps there could be a way to return the link for each photo uploaded if desired perhaps through a text file on the hard disk? This would make embedding of the images so much easier as google has long strings that change even if the folder is made public. I could donate extra!

If one wants to embed multiple images in a blog it is a pain to get the image title for each one.

You can have the plugin open up each image in a browser as it’s exported, so you should be able to just cut-n-paste the URL from your browser. It’s also in the “At PicasaWeb” metadata field in the “All Plugin Metadata” view tagset. Are they not sufficient? —Jeffrey

— comment by Kieran Mullen on February 23rd, 2012 at 7:32pm JST (10 years, 3 months ago) comment permalink

Hi – If I upload an image from my desktop to PicasaWeb will your Picasa plugin “Sync” with the Picasa web album and download into lightroom?

I’ve been using smugmug and picasa (with your plugins) and find I use picasa more so I’m canceling SM., but I just discovered they are promoting a plugin that “Syncs” which i really like …

Anyway, love your lightroom stuff – thanks!


No, it’s a one-way Lightroom-to-PicasaWeb thing. —Jeffrey

— comment by Shawn on February 24th, 2012 at 8:34am JST (10 years, 3 months ago) comment permalink

Oh – one more thing … is there an easy way that you know of to copy the SmugMug albums into Picasa or do i have to recreate each one???


I don’t know of any way to migrate accounts, but it wouldn’t surprise me if someone had built such a thing. —Jeffrey

— comment by Shawn on February 24th, 2012 at 8:36am JST (10 years, 3 months ago) comment permalink

Once I figured out how to use your plugin, Jeffrey, I think it’s pretty awesome! I love how you document how to do damn near everything with it, including associating catalog images with files already on PicasaWeb, Repopulating, etc.!

I have hit only one snag, however, and I am hoping you can help me with it: I cannot tell Lightroom that an image in a Smart Album in your plugin is already published on PicasaWeb. It still thinks it is a “New Photo to Publish”. If it were a regular Album, I could just repopulate, but this is a Smart Album.

The image is already associated with the one on PicasaWeb, so I tried using the “Resend Metadata…” button in the jf PicasaWeb Extras menu item. Unfortunately, it returned “Unexpected HTTP status from PicasaWeb: 404 No album found.” However, I know the album does exist, and it has the exact same name, capitalization and all! Your plugin was the one that created the Smart Album in Lightroom (using dummy criteria at first, of course).

Any idea how to get Lightroom to recognize that this image in the Smart Album has already been published? I don’t want to hit “Publish” again, in case it uploads the image a second time. Thanks!

It would indeed upload the image a second time, so don’t publish it. It’s a limitation in Lightroom, one we can hope will be lifted in Lr4 (and/or Lr3.8), but until then, it’s probably best to not include the photo in a smart collection. —Jeffrey

— comment by Chris McGee on February 27th, 2012 at 1:06pm JST (10 years, 3 months ago) comment permalink

As a prime user of the “out-of-the-box” Flickr add-in that comes with LR3 this is a good solution for users of Picasa. The only disapointment is that with the Flickr tool you can you can create new ‘photosets’ by right clicking the Flickr publish Service, create new photoset, drag photos to be published to it and publish. The solution with this Picasa version is rather clunky and fiddly to publish to a new picasa album as you have to cret the album first via ‘edit settings…’. At least as far as I can see.

Yeah, it’s clunky, but a simple right-click create-album thing simply wasn’t possible when I first developed the Publish parts of plugin, due to a cascade of bugs in Lightroom. I’m still not sure whether it’s possible for a non-Adobe plugin, though with Lr4 coming out, I should check again… —Jeffrey

— comment by Chris Worthington on February 29th, 2012 at 3:57am JST (10 years, 3 months ago) comment permalink

Hi from Viña del Mar (Chile),
I’m a jf-picasa plugin user, since many years and I don’t have any complain, just congrats.

But I have a question: on the version 20111012.173 you wrote, “Include the account id (in addition to the full name that’s already there) in the Publishing Manager login section, to allow multiple accounts associated with the same real name to be easily differentiated”.

I don’t see this on my LR, I just see my name. And since I have at least three picasa accounts (including my google apps acounts) this is/would be a very useful improve.

I’m on (LR3.6) on a Mac with OSX 10.7.3


Only the accounts you’ve successfully authenticated to with the plugin will be listed, so you can run through them… authenticate, logout, then authenticate to another, etc. Then they should all be listed in a dropdown on the login page. —Jeffrey

— comment by Sebastian Fingerhuth on February 29th, 2012 at 8:31am JST (10 years, 3 months ago) comment permalink

Reverse geocoding in LR4 are amazing, saves me a lot of work, but caption template I use in PicasaWeb plugin seems don’t work well with that feature.

When using caption scheme like this: “{Country}. {City}. {YYYY}. {Caption}.” the result is “. . 2012. Example caption.” instead of “France. Paris. 2012. Example caption.”

It is possible for PicasaWeb plugin to use address suggestions like normal (hard) in this situations whenever address fields are empty?

Lightroom doesn’t give a plugin insight into this… it’s all opaque to the plugin, controlled by a catalog setting about whether the suggestions should be used for export. This all seems less than optimal to me, so by all means make a feature request to Adobe… the more who do, the more likely they’ll pay attention. —Jeffrey

— comment by Wieko46 on March 8th, 2012 at 5:50pm JST (10 years, 3 months ago) comment permalink

Plugin version: 20120308.186
Lightroom 4 crashes when trying to upload an 80MB video. The crash happens after Lightroom finishes conversion

Lightroom is not really set up for large exports, and the way Google’s API is designed exasperates the situation. 80MB may simply be too large for Lightroom on your system to handle. )-: —Jeffrey

— comment by Hani on March 13th, 2012 at 1:04pm JST (10 years, 2 months ago) comment permalink

Thanks for your work — I need to move my pictures off Apple’s MobileMe now that it is going away, and your plugin has been immensely helpful.

Suggestion for your copious spare time: integration with Google+, such that I can, for instance, specify that an album is to be shared with my “Family” circle — directly in the plugin, rather than having to go to my Google+ page right after publishing. (In fact, I’d love to specify a default for all albums, and only modify as necessary.)

Another thing I noticed is that Google seems to sort albums according to when they were created, so to get them into the order I want, I have to again go to my Google account and manually set an “album date”. It might be nice if the plugin automatically set that date to the max or min date of all the pictures in the album, when the album is first populated anyway.

Again, thanks for your efforts, much appreciated!

G+ integration will have to wait for Google to provide an API. The plugin offers various album sorts… as many as I could figure out from the data Google provides, so perhaps they don’t provide exactly the same kind of date that they use themselves for the sort? —Jeffrey

— comment by ACK on March 18th, 2012 at 7:45am JST (10 years, 2 months ago) comment permalink

Lightroom 4.0 – Plugin Version: 20100308.186

Publishing to picasaweb includes location info even though I explicitly said not to!?!


To start, great work on these plugins and I love your blog. I am not even sure if this bug I am reporting on is related to your plugin or not, however you probably have more insight than I do as to the root cause.

Ever since I installed Lightroom 4 I have been manually ge0tagging my photos for my reference. The locations I have tagged in LR4 are marked as “private” in the Map module, and I updated the Picasaweb Publish service to “Remove Location Info”, both of which I believe should prevent the location info from being published, yet when I now look at my web album every photo I uploaded now has GPS coordinates. One thing that might be helpful is that my workflow more recently adopted that I also save metadata changes to the file (ctrl-s/cmd-s) after I make them, so the GPS coordinates were also saved to the file and would need “stripped” out on publish (but I am also resizing, etc so it really should be creating a new file anyway…).

Thanks for your help in figuring this out!

The plugin has always (for years) uploaded the geoencoded location with the image, though I suppose now’s a great time to revisit that. Unfortunately it may be a few days before I can push out anything new because the plugin is currently in upheaval due to some really unfortunate (and unannounced) changes Google recently made to how PicasaWeb interacts with outside apps like mine, so I’ve been scrambling to come up with a workaround before it affects too many users. I have to fix that before I can work on other things, but it’s my #1 plugin priority at the moment, so it should be this week, I hope. —Jeffrey

— comment by Aaron Lyons on March 19th, 2012 at 9:38pm JST (10 years, 2 months ago) comment permalink

When I upload images it does not upload the first keyword listed under Keyword Tags.

Windows 7
Version: 20120330.192

Are you sure it’s marked for export? See the info dialog via the context menu in the Keyword panel of Library. —Jeffrey

— comment by Steve Gill on March 31st, 2012 at 5:44am JST (10 years, 2 months ago) comment permalink

Jeffrey, I’d love for the plugin to either let me edit gallery names in LR, or for it to automatically (or semi-automatically, through a Refresh button) get the changed gallery names from Google Photos. I have multiple galleries whose names I’ve changed online but can’t get LR to reflect it. If I remove the gallery and re-add it, I inevitably end up with photos that LR can’t match up to the ones already uploaded, so I’d rather not do that. Thank you in advance for any help with this!

That does seem to be quite the oversight, doesn’t it? I’ve added it to the (oppressively overcrowded) todo list. —Jeffrey

— comment by Raoul Pop on April 8th, 2012 at 11:23pm JST (10 years, 2 months ago) comment permalink

Hi Jeffrey, i would like to use your plugins. It sounds great. I’ve testetd 20120508.199 and some versions before on Windows 7 64bit 4GB rAM with Lightroom 4. I already have 20.000 photos online.

Unfortunatly i could not manage to associate the exiting photos with my catalog. After more then 4 days i canceld the action. It starts on a good speed an then slows down. Fetching the information from Picasa takes about 8 hours on a fast internet connection. Matching online photos with my catalog several days. Is there something i can do to speed up this, or do i’vd to delete my online photos und reupload them with yout plugin?

Regards Nicolas.

Even with 20k photos I wouldn’t expect it to take so long, so there’s probably a bug in the plugin somewhere. You don’t need to associate the images… that matters only if you want to push an update for an image, or if you really want to have Lightroom reflect exactly the state at PicasaWeb. For many users, it’s fine just to use it to push new images. —Jeffrey

— comment by Nicolas on May 12th, 2012 at 4:39pm JST (10 years ago) comment permalink

Windows 7 x64
Lightroom 4.1 RC1
PicasaWeb 20120508.199
From Los Angeles

Fairly consistently, I’m getting the following error:
Unexpected HTTP status from PicasaWeb: 500
GUMBY status=105

It occurs after around 50 pictures or so have been uploaded to Picasa. If I click publish again, it will upload another 50-60ish and then give the error again. So basically I have to just keep republishing until all the pictures have been uploaded. Any help would be great. Thanks!

That certainly seems unexpected, though that “GUMBY” note makes me suspect it’s a problem out of my hands (at Google, or with your networking, such as some kind of firewall or web proxy). Perhaps send a log when you see it next. —Jeffrey

— comment by Eric on May 21st, 2012 at 3:25am JST (10 years ago) comment permalink

Hi Jeffrey, PicasaWeb is awesome, yet I have the following problem.
I keep two catalogs, “Current” with pics on my notebook and Archive with all pics. From time to time I import Current into Archive, but:
– PicasaWeb publish data does not get imported (I guess it may be beyond the scope of a plugin)
So I try to use PicasaWeb Extras … Associate Images Automatically (after making sure all picasaweb albums are imported via PicasaWeb). It runs quite some time, and finds 4 pictures from beginning of this century, but it does not find any picture I have recently exported from ‘Current’ catalog.
I do not rename the file when exporting, etc. I don’t know why this isn’t working for me.
What would be the best way to debug this?

Lightroom ignores publish data during imports and exports, so this is a known (and frustrating) problem, but the “association” is maintained during an import, so no need to associate. When you add new collections in the Archive catalog, be sure to enable the “populate” option, or, for collections already there, click the “refresh” link next to it in the Publish Settings dialog. This should, in theory, bring everything up to date. —Jeffrey

— comment by Dawid on June 11th, 2012 at 4:58am JST (10 years ago) comment permalink

Hi Jeffrey,

Greetings from Chicago!

I manually uploaded a video to Picasa outside of your plug-in because the file was in excess of 100 MB. Then I manually associated it in your plug-in’s extras with the Picasa URL. I can’t find where I mark that file as up to date in Lr, so I can get it out of the queue in the plug-in the be published.

Thanks so much for a pointer to what must be obvious, and I’m just missing it today.


It’s a big kludge, but you have to have it added to the collection via the “claim” feature, rather than putting it in there yourself. It won’t work at all if it’s a smart collection, and my not work otherwise, but is worth a shot. —Jeffrey

— comment by Peter on June 17th, 2012 at 12:09am JST (9 years, 11 months ago) comment permalink

The latest update — so we can make Picasa albums via the Lr context menu — is a treat! Thanks so much for always improving all of these plug-ins. Lightroom would not be the same without you!

Happy Independence Day from Chicago!

— comment by Peter on July 5th, 2012 at 12:50am JST (9 years, 11 months ago) comment permalink

The incorporation of the collections is something I was dreaming for… I used to have many services to keep some order in my catalog and was a nigthmare each time I needed to change a setting… now just a couple of services to keep different setting is enough.

— comment by Rafael Rodriguez on July 15th, 2012 at 6:49pm JST (9 years, 10 months ago) comment permalink

Hi Jeffry

I have installed your last update, and I still can only save 1 (one) authentication, meaning the last one I have authenticated to. I need to navigate between my two accounts because in one downloads are permitted and in the other not.

Love your plugin its my most useful and is a time saver.
Hope you can get around fixing this, since my real name is the same on both accounts and my email is different, why don’t you keep my login ID in the list instead of my real name.

Best regards!

Making a change to how account info is indexed is pretty simple, but it would invalidate the cached data for every user of the plugin, something I’m reticent to do. Also, the kind of data that Google returns is different for G+ users compared to non-G+ users, a change that caused horrific problems for the plugin, and so now that I’ve finally worked around it, diddling with it is another thing I’m reticent to do. Sorry, but for the foreseeable future, you’ll have to make do with an Export presets to toggle logins. —Jeffrey

— comment by Real Mayer on July 22nd, 2012 at 7:20pm JST (9 years, 10 months ago) comment permalink


Is there a way to export to a G+ page and not to the primary G+ account?


I’m not sure what a “G+ page” is, but Google currently has no API to export to G+ anything yet… currently, the best we can do is upload to PicasaWeb and share to G+ from there. —Jeffrey

— comment by Dan on August 13th, 2012 at 10:53am JST (9 years, 9 months ago) comment permalink

When exporting my camcorder’s Videos to picasaWeb, the plugin says :
The exported file “000001234”.m2ts is larger than your picasaweb account limit
The maximum video file allowed is 100MB

But I can upload much bigger files thru picasa’s web interface. Is this size check done by your plugin or by google’s API ?

If this is an check obsoleted by changes in google’s size limits, it would be great to update it !

Google allows up to 1GB through its own upload, but the max through the 3rd-party API is 100MB. The plugin is doing this check before the upload so that you don’t waste the time uploading a gigabyte only to be returned an error. —Jeffrey

— comment by Samuel on August 22nd, 2012 at 7:26pm JST (9 years, 9 months ago) comment permalink

Helly Jeffrey,
Thanks for this wonderful plugin.
First I have a silly question, maybe already replied but I can’t find the answer: after a PicasaWeb album publish, do we need to keep the local copies which were written to the export folder? I noticed it looks like I can remove them with no harm to my published album or original collections. But is there any drawback to this?
Second question: do you plan to add a feature to copy & edit an existing publication service based on the PicasaWeb plugin? This would maybe allow to change the export folder that usually can’t be changed after initial setup, without re-creating the publication service from scratch.
Thanks again for your superb work!

No need to keep the local copies… the default is that they’re deleted automatically (because the default “Export Location” is “Temporary Folder”, which somehow you got switched away from). As for the second question, I think the inability to change the export folder in Publish is an anachronism that I can remove… I’ll look into it. (UPDATE: I had forgotten that Lightroom enforces the inability to change the setting, so there’s nothing I can do about that, so to make a change you’ll have to indeed recreate the whole publish service) —Jeffrey

— comment by Stephane on August 25th, 2012 at 12:02am JST (9 years, 9 months ago) comment permalink

Picasa, 20120820.211

I try to upload videos of 160 mb and the plugin says that google max allowed size is 100mb. However, this is not true because the size was increased to 1GB some time ago, you can check the current values at:

By the way, I also have an album of 1768 photos. As the max number of photos allowed by google is 1000 (as of today) when I upload the first 1000 I get a “403 error” from google. Could you add a check on how many photos the album has to say a more friendly error like “Google has a limit of 1000 photos per album, sorry” or something like that.

Many thanks

Google allows up to 1GB through its own upload, but the max through the 3rd-party API is 100MB. The plugin is doing this check before the upload so that you don’t waste the time uploading a gigabyte only to be returned an error. I’ll take a look at a better error message… —Jeffrey

— comment by Roberto Alcazar on August 31st, 2012 at 1:16pm JST (9 years, 9 months ago) comment permalink

Hey Jeffrey,
Thanks for making the world a better place to work in!! I’m writing from California high in the Sierras. Re: picasaweb-20120820.211, Maybe this is a no brainer, but unlike your facebook plugin, I can’t seem to find a way to publish to a google plus page associated with my account. Am I missing something or is it not an option?
-Erik J

Google has not released a publishing API for G+ yet. —Jeffrey

— comment by Erik Johnson on September 1st, 2012 at 3:53am JST (9 years, 9 months ago) comment permalink

Current version is having issues. I made the folder within plugin, it chugs away and the processing and uploads. Then opens up the browser in a new window with 0 photos. So where was it uploading them to?

Odd that it sent you to the wrong page (or that the right page was empty). In Lightroom’s Library, check out the “All Plugin Metadata” metadata view and look for the “At PicasaWeb” item for one of the photos, and it should send you to the actual photo online. Hopefully that’ll help track things down. (Is it possible that you’re not logged in to your account via the browser, so you’re viewing the gallery of images that are private?) —Jeffrey

— comment by Kieran Mullen on September 6th, 2012 at 12:53pm JST (9 years, 9 months ago) comment permalink

Writing from California.

One snafarkle that I encounter with upload to Picasa plug in (downloaded latest version today) has to do with updating a Gallery that was created using an export with sequence numbers. I use sequence numbers to establish the logical sequence of the pictures by rearranging photos in a LightRoom collection before I export to a new Gallery. Works like a charm for the original upload and I can always re-sort the Gallery in Picasaweb if I change something.

However, when I update a few pictures from the collection the uploaded images are assigned new sequence numbers based solely on the pictures to be uploaded. Ideally, I would have an option to re-use the old sequence numbers when updating.

I recognize that this option is not useful when I add new images to the collection, but suggest that the update-only case happens frequently enough that it is worth the complications of having another option.

Thanks in advance.

There is, essentially, no right way to do what you want. Lightroom doesn’t allow for it (the file-naming stuff is all built in, so whatever it does with sequence numbers is what it does). But in the parallel case of my collection-publisher plugin, I go to great lengths to “do the right thing” when the user wants sequence numbers in the filenames, but no matter what I do, someone comes up with a use case for something else. It’s a lose-lose situation to use sequence numbers in Publish. Overall, the right way to do this would be for the plugin to tell Google the explicit order found in Lightroom, but Google does not support this. 2½ years ago they said this support was coming “soon”. —Jeffrey

— comment by Wes on September 24th, 2012 at 3:06am JST (9 years, 8 months ago) comment permalink


I have the PicasaWeb export plugin (20121014.216).

I lost my C drive and had to rebuild.
The plugin has reverted to ten-at-a-time mode.
How do I fix?


If your Lr serial number has not changed, just use the “lost your code?” button in the registration dialog, and you can re-register using your old code. —Jeffrey

— comment by Winston Mitchell on October 16th, 2012 at 12:23am JST (9 years, 7 months ago) comment permalink

Hi Jeffrey (writing from Manhattan) – I’ve been using your facebook plugins for a while and have loved them, and am looking to switch to google+ but am having issues with the picasaweb plugin for lightroom 3 on mac – when creating a new album w/ the facebook plugin it asks for a local album name and a facebook album name, but the picasa pluggin only seems to ask for local name. When I create an album and hit “publish”, I get the error:
picasaweb#216 +2193.4: [x119a597f8] @Export line 834:
Missing destination cookies:
[x119a597f8] @Export line 834
[x119a597f8] @Debug line 1254

Debug:757: Assert @Debug:757
Am I doing something wrong? I just upgraded to make sure I’m up to date – version is 20121014.216

I’ve made a FAQ for this issue —Jeffrey

— comment by Eric C on October 16th, 2012 at 12:50pm JST (9 years, 7 months ago) comment permalink

Hi Jeff. How do I rename a Smart Album under Picasaweb?
I did rename the album in picasa and the extension settings did pickup the change but I still see the old name in the list. Thanks!

Collection rename isn’t supported yet (there are bugs in Lightroom’s plugin infrastructure that makes it problematic). At this point, if you need the new name, I guess you can delete the collection then re-add it via its new name, choosing the “Populate” option. —Jeffrey

— comment by Roberto on October 17th, 2012 at 6:25am JST (9 years, 7 months ago) comment permalink

Hi: Do you plan to insert “name of the album” token?. It should be really useful. Thanks

This is perhaps possible, but a bit problematic with how things are built under the hood. I’ll give it some thought… —Jeffrey

— comment by Alvaro on October 18th, 2012 at 4:14am JST (9 years, 7 months ago) comment permalink

No need to do this just configure Picasa as an external editor inside Lightroom and Bob is your uncle.

— comment by Charles van Dijk on October 18th, 2012 at 2:19pm JST (9 years, 7 months ago) comment permalink

As I understand the PicasaWeb Plugin. New Picasa Albums must be created by editing the plugin Settings. And this in turn creates a Publish Service Collection/Smart Collection or both. A Right Click on any PicasaWeb collection present the context meny that permits the Import of Smart Collection Settings creating a nes Publish Service collection that does not point to an existing PicasaWeb Album. Publishing this imported Smart Collection fails and I can understand why. If I create a Smart Collection and PicasaWeb Album via editing the Publish service settings, I get a default generic Smart Collection which can not be renamed. Is there a way to import an existing “lrsmcol” file into the existing smart collection created with the edit of the PicasaWeb Publish Service?

All of my Publish Services are managed by smart collections with complex queries so that they self populate. I can share these complex smart collections by exporting them from one Publish Service and importing them into another and modifying them slightly and (usually) renaming. This works well with all of the other ‘jf’ Publish Services but not the Picasa Web due to the restrictions notes above and I suspect imposes by the PicasaWeb API or LR.

No, sorry, this is a problem with Lightroom’s plugin infrastructure. Creating a smart collection that way does not work with any of my publish plugins… I can imagine only the most simpleton plugins could make that work. It’s really a poor design, but there’s not much I can do about it. )-: —Jeffrey

— comment by Cletus Lee on November 5th, 2012 at 12:06am JST (9 years, 7 months ago) comment permalink

Great plugin1

I attempt to publish but get error:

47 photos have been excluded because they’re off line.


Sounds like they’re on an eternal disk that’s not attached? —Jeffrey

— comment by David on February 9th, 2013 at 11:22pm JST (9 years, 4 months ago) comment permalink

I would like to insert blank lines into my captions and I saw you can do this with newlines. I tried every combination of \r and \n that I can think of and can’t get it work. Can you give me an example of how you would use newlines to insert blank lines in caption templates. Would you just repeat the code if you want to insert multiple blank lines? Thanks!

Actually adding a blank line (via control-enter) or using <br> should do it. —Jeffrey

— comment by Greg Forcey on February 12th, 2013 at 9:07am JST (9 years, 4 months ago) comment permalink


Everytime I try to open the .zip (i am on mac os X), I got an error message. Impossible to open your zip(s).

From Australia

I don’t know what to tell you… tens of thousands of OSX users have no problem with my zips. Perhaps try downloading with a different browser or ISP. —Jeffrey

— comment by bobby on April 17th, 2013 at 11:33am JST (9 years, 1 month ago) comment permalink

New York
Tried to create new album in Picasaweb. Getting message “corrupt collection settings”. Not getting drop down in Lightroom for “authentication code”. Have been using successfully for years. Problem seems to be with Google Plus. How can I correct, or, revert????

This sounds like a form of this bug. If you can’t revert to a backup catalog, the best I can suggest is to delete and recreate the collection. )-: —Jeffrey

— comment by carl meisel on April 30th, 2013 at 3:03am JST (9 years ago) comment permalink

Catalog seems OK and backups indicates integrity OK. Haven’t created any new collections recently. Don’t know what message is referring to. Somehow Google changes my name in your system. Could that be the culprit?

New York

As best that I can tell, Lightroom sometimes corrupts/loses the internal plugin data for a Publish collection. It’s relatively rare, but once it happens, the plugin can’t work with the collection. )-: —Jeffrey

— comment by carl meisel on April 30th, 2013 at 11:45am JST (9 years ago) comment permalink

Version 20130520.233

I’m new to video. I just tried uploading two videos to Picasaweb and the first got rejected because (according to the message) it was larger than 100MB.

I searched the web and it appears as if the limit is 1G. Do I need to enable something somewhere? The finder says it is 233MB.

Thank you for your time,

As noted multiple times above, Google allows up to 1GB through its own upload, but the max through the 3rd-party API is 100MB. —Jeffrey

— comment by Perry Smith on May 20th, 2013 at 11:06pm JST (9 years ago) comment permalink

My photo camera Olympus E-620 fill the Caption-field by value “OLYMPUS DIGITAL CAMERA”. I do not like it and I set the option in the plugin “jf PicasaWeb” – “Settings:” – “PicasaWeb Metadata Management:” – “Image Caption…” – “Caption = None”. When the plug-in exports photos the first time to the PicasaWeb – all right, Caption-field is blank in the Picasa. But when I repablish any photos Caption-field = “OLYMPUS DIGITAL CAMERA” in the PicasaWeb.
Please fix it.

I don’t think the plugin would ignore your settings for a republish, but I’ll take a look. But it would be much better for you to set an import metadata preset to clear out that silly caption. —Jeffrey

— comment by Dmitry Bulgakov on June 11th, 2013 at 12:07am JST (9 years ago) comment permalink

Clear. Thanks for a good idea.

— comment by Dmitry Bulgakov on June 11th, 2013 at 11:19pm JST (9 years ago) comment permalink

I do hope that Google+ Photos API comes along soon. Photos from my Samsung Note II I want auto-enhanced, so I have this as my default, but those that come from the Lightroom I don’t want to apply enhance automatically so it would be great to have the plugin disable it before upload and re-enable it afterwards.
I don’t know if Picasa API exposes this?

The PicasaWeb API hasn’t changed in years. The lack of a G+ API this long (2 years?) into the service is surprising; and perhaps telling. —Jeffrey

— comment by Andy Austin on June 16th, 2013 at 10:44pm JST (8 years, 11 months ago) comment permalink

I do not think there is much future in picasa API or picasa as it stands. Everything is moving to g+ and gdrive. Note that in g+ you can add pics via gdrive so why not add this as an option and avoid all of the limits. Workflow would be LRto gdrive to picasa. Atleastan option for. Large videos.

Well, I do have a Google-Drive plugin that you can use as well. —Jeffrey

— comment by Shawn on June 17th, 2013 at 7:11am JST (8 years, 11 months ago) comment permalink

Hi — I’m having trouble downloading your plugins via Chrome on Mac. It seems to work fine in Safari, but for some reason in Chrome it just goes back to the plugin page. Is this a known issue?

It’s not known by me… have not heard any other reports of it. —Jeffrey

— comment by Matt on June 18th, 2013 at 2:23am JST (8 years, 11 months ago) comment permalink


I emailed you yesterday regarding the “corrupt collection settings” error with the picasa plugin and LR5. I was able to cure the problem by performing a new authentification with picasa rather than choosing my existing username from the drop down menu during setup.

— comment by Steve on June 23rd, 2013 at 8:22am JST (8 years, 11 months ago) comment permalink

Wanted to report what I believe is a bug in the PicasaWeb plugin. I made a new virtual copy of a photo I had published through the plugin, and now the plugin wants to treat the new copy as an updated version of the photo. I can’t even delete the new copy without it asking me whether I want to delete the photo from the publish service. Any idea what’s going on?

This is an unfortunate side effect of Lightroom not giving the plugin any control over what plugin data gets copied to the new virtual copy. If you make a virtual copy after having published/exported an image, you should clear the plugin data for the copy via “File > Plugin Extras > PicasaWeb Extras > Clear”. It’s ridiculous, but I asked Adobe for help about this years ago, to no avail. —Jeffrey

— comment by Noah on June 23rd, 2013 at 10:45am JST (8 years, 11 months ago) comment permalink

Hi Jeffrey
When I am exporting to Picasa in Lightroom 4, I am getting an error saying that the plug in cannot render because it cannot find my photos. Perhaps its been deleted or offline.
Any suggestion as to how to fix this?

I suspect Lightroom is telling you that it doesn’t know where your files are because it doesn’t know where your files are. Did you move them after pointing Lightroom at them? Delete them? Are they on a disk that’s not available at the moment? When you “show in Finder/Explorer”, do you see the files? —Jeffrey

— comment by Anthony Rynne on July 22nd, 2013 at 8:07pm JST (8 years, 10 months ago) comment permalink

In the metadata that is added by this plugin there is the field ‘PicasaWeb Upload Date’ however when you try to use this date in a smart collection it doesn’t give you the usual date options of , before, after etc, it looks as if it sees this date as text and allows you to use text operators only (such as contains, contains all etc). Is this a bug? Can it be changed so that it is seen as a date so that normal date operations can be performed… this would have saved me a lot of time in a smart collection I was setting up.

many thanks

Win7, Lightroom 5.0, PicasaWeb plugin 20130701.241

Scott Masterton, Scotland.

Sadly, Lightroom doesn’t let me tell it that the date is a date, so yeah, it’s only a text field that I just happen to write the date to. —Jeffrey

— comment by scott masterton on July 29th, 2013 at 5:01am JST (8 years, 10 months ago) comment permalink

Hi Jeffrey,
I am curious to understand whether it is possible to actually sort the picasaweb collections in Lightroom by name first. Much apologies if I overlooked this setting, but it appears that the sorting is by collection type (all smart folders first then regular collections) first, then by name. Can this be changed?

I am on version 20130701.241

Thank you in advance!
Regards, maik

The plugin has no insight here, so it’s whatever Lightroom allows, and to my knowledge, there’s no control over the display order. —Jeffrey

— comment by Maik on August 6th, 2013 at 6:47pm JST (8 years, 10 months ago) comment permalink

Hi Jeffrey,

love your plugin!
One small question (hope I didn’t overlook an answer in the FAQ)… is it possibe to sync the custom picture order of the LR collection to PicasaWeb (just like if I use organize there)?

Thanks in advance

No, Google doesn’t allow for it. —Jeffrey

— comment by Dietmar on August 18th, 2013 at 8:35pm JST (8 years, 9 months ago) comment permalink

Hi Jeffery!

I’m writing from New Jersey regarding the Picassa plugin. I am using Lightroom 3 on a Win7 PC. I experienced the “missing destination cookies” error so, as instructed in the FAQ, I deleted the Publish Service and set it up again from scratch. Now I am receiving the “corrupt collection settings” error when trying to publish. What can I do to fix this?


The 2nd error is just a more general, less specific version of the first. Something seems corrupt about the entire publish service. )-:   I can only hope that if you create a new one (perhaps before even deleting the original) that it’ll be free of the corruption. I just don’t know; the plugin is as much a victim as you. )-: —Jeffrey

— comment by Dan on September 9th, 2013 at 1:46am JST (8 years, 9 months ago) comment permalink

I tried images association and I have some problems/questions/suggestions:
Is there some bulk visual comparsion all associated (not only in collection) images with images on picasa (not only url, but image)?
Is it possible to disassociate incorrectly associated image?
Is it possible to create collection derived from albums of associated images?
Is there some association log?
Best regards, Pepa (CZE)

You can disassociate an image via the “Clear” button in “File > Plugin Extras > Picasaweb Extras”. You can make a smart collection via the “Uploaded to PicasaWeb” key. The plugin log gets filled with lots of stuff as the association process is going on, but it’s perhaps not very easy to understand at a glance. —Jeffrey

— comment by Pepa on September 17th, 2013 at 3:08pm JST (8 years, 8 months ago) comment permalink

i upgraded to LR 5.2 and found that plugin i had installed earlier this year no longer worked. so i downloaded the most recent version, 0926.248 and tried to install this. using plug-in manager, i chose add (having deleted the old version from LR) and then selected the win folder within the unzipped downloaded file.
i got the error message “an error occurred hile attempting to load this plug-in.”

what am i doing wrong?

See this FAQ. —Jeffrey

— comment by tony mischel on September 28th, 2013 at 3:26am JST (8 years, 8 months ago) comment permalink

Can you help with this message…….I have just upgraded to 5.2 and also the plugin but am now getting this message

Couldn’t render image: Invalid parameter name: ColorNoiseReductionSmoothness


That sounds like an issue with Lightroom’s render engine; I suspect it happens with a vanilla to-disk export. I’d suggest submitting it to Adobe. —Jeffrey

— comment by Anthony Rynne on September 30th, 2013 at 8:15am JST (8 years, 8 months ago) comment permalink

Hello Jeffrey!

Is it possible to authenticate with this plugin against my Google+ page account?
Reason is – I’ve created a Google+ Page and would like to publish photos from LR5.2 to an Album on this site directly.

Thanks for your advice!



Google still hasn’t provided an API for G+, so you still have to go through PicasaWeb, but PicasaWeb albums show up in G+ automatically, so you can get something pretty close that way. —Jeffrey

— comment by Albert Dandl on October 11th, 2013 at 2:27am JST (8 years, 8 months ago) comment permalink

hi, I am using picasaweb export plugin with lightroom 5.
I am trying to upload RAW (nef) photos to picasaweb but get the error
PicasaWeb does not accept “.nef” files for upload; aborting.

The thing is picasaweb DOES support .nef files since recently.

Using version –> 20131023.250


Their upload API still does not. I gave it a try on the chance that their docs were out of date, and it did not work. —Jeffrey

— comment by bonald on November 1st, 2013 at 2:49am JST (8 years, 7 months ago) comment permalink


I Like your plugins and have found them very useful!

I have comment or a question regarding the way Lightroom utilizes Export Plugins.

I often prepare sets that I want to share in several channels. I might want to share the same set:
1) on my hard disk to be syncronized via iTunes with my Apple TV in the living room
2) on Adobe Revel to show people from my iphone or iPad
3) on Facebook
4) on Picasa

I imagine having a set and then it should be able to tick boxes for each earlier preset channel.

Is there a way to send and update a set in several channels with your plugins or in some other smart way?

The short answer is “no”, Adobe doesn’t expose hooks that make it feasible. If there are common patterns of how you want to export, perhaps do it with keywords. It’s an unsatisfying answer, I know. —Jeffrey

— comment by Nils on November 13th, 2013 at 5:44am JST (8 years, 6 months ago) comment permalink

I’ve abondoned Picasaweb in favour for another web service.

Is there a way to clear the “info.regex.lightroom.export.picasaweb2.history” ?

Select relevant images and invoke File > Plugin Extras > PicasaWeb Extras > Clear” —Jeffrey

— comment by Mikael on December 1st, 2013 at 6:27pm JST (8 years, 6 months ago) comment permalink

Hi Jeffery,
I recently switched from a pc to mac and reloaded your most recent plugin in LR5. After editing many photos I have been reloading some to Picasa. Under “One image has been selected for import” in the Picasa Web: Meta data management section, the “replace the most-recent previously-uploaded copy” has been ticked. But it’s not replacing it like it did before on my pc, It’s just adding the new double copy. Is there possibly an issue because the images were not originally uploaded with my new computer?

Portland, OR USA

If you copied over the catalog from the old computer to the new, all the upload history should be with it, so I’d expect it to work. When viewing the photo in Library and selecting the “All plugin metadata” metadata-view preset, do you see “Uploaded to PicasaWeb: yes”? —Jeffrey

— comment by Randall on December 14th, 2013 at 8:21am JST (8 years, 5 months ago) comment permalink

I’m getting a new computer (yeah) and I’d like to know the best way to migrate ALL of my library to the new one and, also, to make sure that the photos that I’ve published with PicasaWeb remain connected afterwards. How do I go about this? And thanks for this great product.
Sorry I posted on the wrong page, earlier.

Copying your catalog (the *.lrcat file) should do it as far as the PicasaWeb data, though don’t forget the master image files too. 😉 Copying your Lr preferences file would be good too, though all that info can be reubilt as needed. —Jeffrey

— comment by Keith Vandenbergh on January 26th, 2014 at 10:58am JST (8 years, 4 months ago) comment permalink

I’m trying to download and unzip your Picassaweb plug-in for Lightroom 5.3. I can download it but don’t seem to understand where to put it or how to unzip it to make it functional. Can you help?

See the install-instruction link in the upper-right of the page. —Jeffrey

— comment by David on February 13th, 2014 at 7:46am JST (8 years, 3 months ago) comment permalink

Hi from the Bay Area, CA.

I’m a new user of your PicasaWeb plugin and I have a question about workflow. Naively, I’d like to build Collections in LR and then mirror these to the Publish Services of my choice (PicasaWeb, Facebook, etc.). But it’s not clear to me how best to do this (or, stepping back, whether this is even a sensible workflow; I’m new to LR too).

One approach seems to be making a Smart Album in the PicasaWeb service matching the LR Collection of my choice. So far I’ve been unable to figure out how to make a Smart Album due to the “bug” noted in the Create Smart Album dialog. (It says to use the “Edit Settings…” dialog but I don’t see how to do this from within that dialog.)

The other approach is to make regular Albums and add all the photos from the respective LR collection, but this doesn’t keep up with changes to the underlying LR collection.

Any suggestions on how to achieve this or advice on what I probably actually want (from the perspective of an experienced user) are most welcomed.


Within the “Edit Settings” dialog, next to the name of the target album, click the “smart” checkbox, and it’ll create a smart collection with dummy rules. Then you can edit the rules to with something like “Collection contains …..”. —Jeffrey

— comment by Mark P on March 3rd, 2014 at 11:12am JST (8 years, 3 months ago) comment permalink

I am exporting from smart previews (long edge set to 2048) and all the images end up being smaller than that and all with a different sizes, ranging from 1915 to 2010 pixels on the long edge. This happens with the current version and with the previous version of the plugin.

Windows 7, Lightroom 5.x, 20140204.252

The sizing is all done by Lightroom, so whatever results you get would be the same with a vanilla “Hard Disk” export. Perhaps you have the “don’t enlarge” option set? —Jeffrey

— comment by Dorin Nicolaeascu-Musteață on March 11th, 2014 at 7:46pm JST (8 years, 3 months ago) comment permalink

Hello from Texas. Lightroom 5 and Picasaweb version 20131023.250.

I do not have any of the boxes checked under “Metadata that triggers Republish” but whenever I change or add a keyword to an already published image, it goes back into the queue for republish. What am I missing?

I know I’m a couple of versions back but I didn’t see anything about this as being updated since my version.

Thank you!

It’s not your fault… this part of Lightroom has been horribly buggy since day one. )-: —Jeffrey

— comment by Terri on March 26th, 2014 at 5:07am JST (8 years, 2 months ago) comment permalink


I’m using latest Export to PicasaWeb (20140422.254) with Lightroom 5.4 on Windows 7 64bit.

When I’m uploading mixed set of pictures and 1 video to PicasaWeb, there is an error about video file size being over 100M (it is around 340M). However, after checking some web resources it looks like the maximum file size for picture is 100M and 1G for video. Are picture and video files being mixed somehow here, should the plugin be able to upload 300M video to PicasaWeb?

Thanks for wonderful plugins!

Their limit for 3rd-party apps is more restrictive. I’ve just added a FAQ about it. —Jeffrey

— comment by Otto K on May 1st, 2014 at 3:14pm JST (8 years ago) comment permalink

Thank you for that feature rich and well done plugin!

For picasaweb video uploads failing because of the 100MB limit it would we great, if you could implement a “size down to fit” option, which automatically retries rendering and upload with a lower quality, when the google API limit is exceeded. Perhaps that can be implemented in the failure dialog window or as an option setting in the video section.

Unfortunately the plugin has no control over that… and considering how long it takes Lightroom to render a video that big to begin with (a long time), redoing it over and over to find the right settings would take forever. What’d be best is if it could provide a reasonable estimate of the size before you actually render… —Jeffrey

— comment by Martin on June 3rd, 2014 at 3:14pm JST (8 years ago) comment permalink

Do you answer cries/pleas for help?

Often. —Jeffrey

— comment by Dick on June 12th, 2014 at 4:27am JST (8 years ago) comment permalink

The plug in does not post photos with my watermark even though it’s set in the Export instructions. I’ve repeated the process several times with the same result. What’s up?

Any chance you have the Image Format set to “ORIGINAL” instead of “JPEG”? Adobe has inexplicably made that mean “Original pixels with catalog metadata”. —Jeffrey

— comment by dylan mcclintock on July 4th, 2014 at 1:54pm JST (7 years, 11 months ago) comment permalink

Hello from Italy,
you’re simply the best, very good job.
Now I’m trying the plugin and just trial period expires I will definitely donate to the work done

— comment by ripperhack on July 9th, 2014 at 8:58pm JST (7 years, 11 months ago) comment permalink

I love the Export to Google+.
I have now a Google page, but I am not able to upload to the Google Page.
It this not posssible ?

I don’t know anything about “Google Page”, but considering that Google hasn’t released an API for Google Plus yet (the plugin works through its old PicasaWeb API), I wouldn’t expect any support from Google soon on an API a plugin could use. —Jeffrey

— comment by Jorn Jensen on July 13th, 2014 at 12:33am JST (7 years, 10 months ago) comment permalink

Lightroom version 5.5.0 build 968504 for Windows Windows 7 Home Premium Edition (x64)
Jeffrey’s picasaweb plugin for Lightroom, version 20140715.265

Uploading via the plugin does not trigger Picasaweb’s “Notify these people when photos are uploaded to this album” option that applies to albums that have been shared. Is this something you can check into? Thanks!

I just checked, and the API the plugin must use has no mention of any notification thing, so it’s not something I can enable. If they’re not honoring the album setting, it’s likely a bug that you should report to them. —Jeffrey

— comment by Doug on July 23rd, 2014 at 12:35pm JST (7 years, 10 months ago) comment permalink

Thanks for the great utility…This may be more of a question for Google/Picasa, but it seems Picasa insists on adjusting (saturation, contrast, etc.) uploaded photos to their site. I don’t like this. I’ve not been able to find a way to turn this ‘feature’ off via picasa. Do you happen to know of any solutions for this?

I don’t think they make those kind of adjustments automatically, but it wouldn’t surprise me if they had that kind of feature. I’d expect it to be opt in, though, if they added such a thing. —Jeffrey

— comment by Darby on August 4th, 2014 at 1:59am JST (7 years, 10 months ago) comment permalink

A comment re:

There is a setting called auto enhance which is buried deep in your Google + profile settings. Switch it to off. And yes, they totally do stuff to your pictures. 🙂

— comment by Jukka Lariola on August 26th, 2014 at 4:37am JST (7 years, 9 months ago) comment permalink

Every interaction with Google is producing the error “Unrecoverable server error at Google (it returned a normal web page instead of the proper API reply).” I get this when I refresh the album list or try to create a new album. I am using LR 5.6, and I just updated the plugin to the latest version. Is there a problem with PicasaWeb or did Google change something that broke the plugin? Thanks.

A number of folks have reported this suddenly. I suspect a bad server at Google. Hopefully the problem will just go away sooner than later. —Jeffrey

— comment by Kurt on August 26th, 2014 at 12:58pm JST (7 years, 9 months ago) comment permalink

Due to APIs then, no chance of a plugin publishing to G+ Business page?

Until Google opens up APIs to G+, the plugin can publish only to PicasaWeb. For the last few years they’ve had PicasaWeb feed to G+ pages, but I don’t know whether that applies to G+ business pages… —Jeffrey

— comment by Nick on November 6th, 2014 at 7:33pm JST (7 years, 7 months ago) comment permalink

I had to do a restore on my Win7 Pro OS. Beforehand, I backed up as much as I had thought of. Looking in my LR5, I see under “publish services,” this: ” jf PicasaWeb (missing plug-in) : Picasaweb,” and under this several folders I had been working on. The images are intact.

What do I do, just download and install the current version? I can’t find the receipt you sent me for my contribution at the time of my first download. Does it matter? Thanks.


Yup, just download the latest version and put it where it had been, or into wherever you want it to live then point the plugin manager at it. —Jeffrey

— comment by Dick on November 18th, 2014 at 5:02am JST (7 years, 6 months ago) comment permalink

Hi from Greensboro, NC!

I received a message saying that the video I was uploading was larger than the PicasaWeb account limit of 100MB – the file is 128MB. But, in searching online, I believe the actual video limit is 1GB (if not larger). Is there something else going on?


Their limit for 3rd-party apps like the plugin is smaller than their limit for their own apps. —Jeffrey

— comment by Bobby on December 7th, 2014 at 1:23am JST (7 years, 6 months ago) comment permalink

I’m trying to set up a publish to my picasaweb, but when I put photos into my smart collection and publish it comes back with an error message that says: “PicasaWeb does not accept “.dng” files for upload; aborting.”.

I thought picasaweb works with .dng files? Am I doing something incorrectly?

PicasaWeb works only with JPEG, PNG, GIF, and BMP. Their Picasa desktop app works with DNG, but that’s the desktop app. —Jeffrey

— comment by Ivan on December 15th, 2014 at 8:43am JST (7 years, 5 months ago) comment permalink

First of all, thanks for great plugins – I use quite a few of them, and these are incredibly useful. Recently, I started to use PicasaDesktop app to tag faces in all my photos (as a first step in my workflow), to import it then into LR and then publish (to a few places, but importantly, to PicasaWeb) directly from LR using your jfPicasaWeb plugin (the latest version). This process works really well for keyword tagging (I use AvPicFaceXmpTagger to propagate Picasa tags into XMP; I also tried writing into XMP directly from PicasaDesktop). Now, PicasaDesktop also creates metadata for face regions (rectangles outlining faces with name tags), and when I use PicasaDesktop to upload to PicasaWeb this information is preserved (I can see face regions with proper names). However, if I use LR with jfPicasaWeb to upload the same file (that definitely contains face region metadata in all known formats), then I get the proper face rectangles in PicasaWeb, but all names turn into “Unnamed”. I don’t think this is an issue with jfPicasaWeb per se, as the same thing happens if I upload the same file into PicasaWeb directly (it seems that PicasaWeb ignores face nametag metadata). No matter what kind of metadata manipulation I performed on the uploaded file, the only way to get properly named face regions in PicasaWeb was to upload with PicasaDesktop.

First question, am I doing something wrong? 😉

If not, then I suspect that PicasaWeb is ignoring face nametags in metadata, and PicasaDesktop uses separate API calls to set these up on uploaded photos (there is even upload status line ‘syncing face tags’ or something like that). It seems that somebody looked at some of the face tag Picasa API:

Would be great to get face regions working. I am even contemplating exporting output from the publishing sets into a folder, and then upload with PicasaDesktop. I would really prefer not to – sync provided by jfPicasaWeb publishing sounds awesome. Can it support face regions?


Unfortunately this is unlikely to get solved soon. The plugin doesn’t have easy access to the XMP data, and it would be a lot of work for few people. I’d bump it up in priority if face tagging ever gets more mainstream… —Jeffrey

— comment by Victor on January 21st, 2015 at 1:15am JST (7 years, 4 months ago) comment permalink

Hey, cheers for this plugin, very helpful!

I only found an old comment about this, so wanted to check whether this is still true:

Videos that are larger than 100 MB and uploaded and associated manually cannot be marked as published in Smart Collections.

Do you have an elegant workaround for that? For now, I’m thinking to just exclude videos from the smart collections.

Thanks again!

PS: Saw that you’re living in Kyoto – nice man! I’m currently contemplating moving to Japan myself!

I can’t think of any workaround, much less an elegant one, sorry. —Jeffrey

— comment by Jean-Marie Schlömer on January 27th, 2015 at 6:25pm JST (7 years, 4 months ago) comment permalink

Thanks Jeffery for making this plugin available. I’ve just begun using the plugin for Google+ (v.2015-206.279) and it seems to be working properly, EXCEPT for the ‘automatic’ publish feature which should be re-publishing based on further development, as well as changes to chosen metadata, but it doesn’t work. I don’t see anyone else complaining about this, so I must have done something wrong(?) Could it be that I changed the default “temporary” location to a folder I wanted to keep track of? …TIA!…

The “metadata that triggers republish” stuff has been flaky since it launched. I’ve submitted bug reports to Adobe, but well, no fixed yet. Lots of complaints across many plugins, so you’re unfortunately not alone. )-: —Jeffrey

— comment by michael shaffer on March 2nd, 2015 at 4:47am JST (7 years, 3 months ago) comment permalink

Hi Jeffrey,

Any target date for when your plugins will support LR 6 (CC) ???

Modern versions of all my plugins should work fie on Lr6. ‐Jeffrey

— comment by Ron Donson on April 22nd, 2015 at 5:59am JST (7 years, 1 month ago) comment permalink

After upgrading to Lightroom CC, I get a popup with the message “Lightroom needs to configure your system for the $$$/x289=jfPicasaweb plug-in.” After clicking OK, it then runs a command prompt with lightroom.exe -register. The first couple of times, this action completely froze my computer and I forced a reboot. I finally let it run for quite a while and it finished doing something, but the prompt still appears every time I start Lightroom and now it doesn’t seem to do anything. I did try completely removing the plugin and re-installing it, but nothing changed. depsite the persistent prompt, the plugin is working just fine.

Thanks for the awesome plugin,
Jeff from Texas

The word from Adobe on this is that if it keeps coming up, either reinstall Lightroom or run “lightroom.exe -register” as an admin. —Jeffrey

— comment by Jeff Stovall on April 24th, 2015 at 6:08am JST (7 years, 1 month ago) comment permalink

Aloha Jeffrey,
I downloaded your google plus plugin for LR yesterday. Works great. How would I publish pics from LR to other google pages I have?

Mahalo in advance

Not until Google creates an API for G+, which after all these years stills seems unlikely. The plugin actually publishes to PicasaWeb, which Google then mirrors to your primary G+ page. —Jeffrey

— comment by Kiaaina Wong on April 29th, 2015 at 11:10am JST (7 years ago) comment permalink

Hi, with LR 6 I do get the following error message when starting LR up: “Lioghtroom needs to configure your system for the $$$/x289=jf PicasaWeb plug-in”.

Tried to reinstall several times, no help.

All the other plug-ins work fine.


Please see this FAQ. —Jeffrey

— comment by Fredi on April 29th, 2015 at 6:19pm JST (7 years ago) comment permalink


Thank you so much for your plugins; I have been a happy user on all my LR instances for years. I am using the automatic reverse geocoding; which previously never worked, so I had given up trying to construct export templates with location info. But thought I’d try again with the latest versions of LR CC and current picasaweb exporter. I’ve read all the comments I could find that seemed relevant (and which gave me some hope it may now work) and have been careful to ensure all the selections for privacy and inclusion are appropriately set. But still no location information in the exported titles.

I am feeling a bit stupid; am I missing something or is there still no way for the plugin to access the reverse geo-coded data?

cheers Rod

Lightroom’s automatic reverse geoencoding doesn’t become “real” until you confirm it (I suppose by selecting photos then putting keyboard focus into the field then hitting ENTER), but there’s an option in the Catalog Settings that makes it automatic: “Export address suggestions whenever address fields are empty”, in the Metadata tab. —Jeffrey

— comment by Roderick Laird on May 9th, 2015 at 6:04pm JST (7 years ago) comment permalink

Picasaweb and Ipernity plugins were working fine till I upgraded my LR5 to LRCC (6). I’m running Win7 SP1 x64, and LR is x64 as well. After I upgraded, both Picasaweb and Ipernity would display the following message *every time I start LR”. Initially I clicked OK, and an elevated command window ran and exited so quickly I couldn’t see what happened. I soon discovered that this error displays every time I run LR, so I uninstalled both plugins. I was hoping the latest update would resolve the issue, so I just installed it only to find the same error is generated. I can’t attach a screen shot, so here’s the error: “Lightroom needs to configure your system for the $$$/x289=jf PicasaWeb plugin.” Sadly, once again I just uninstalled both plugins. Flickr and the other plugins I use all work fine. Thanks for your help!

Please see this FAQ —Jeffrey

— comment by Margaret on May 18th, 2015 at 3:32am JST (7 years ago) comment permalink

Just a note for those still experiencing issues with the export plugins after upgrading to CC/6. “lightroom.exe -register” did not work for me. I had to completely uninstall Lightroom with the option to remove all settings, then reinstall Lightroom and the plugin. Be sure to save your presets before uninstalling. This was a frustrating issue and cost me many hours.

— comment by Jeff Stovall on May 18th, 2015 at 10:23pm JST (7 years ago) comment permalink

I’m sure you’ve already thought of it 🙂 Can we get face regions exported in the PicasaWeb plugin?

Kind regards,

— comment by Øystein Mehus on May 21st, 2015 at 6:52pm JST (7 years ago) comment permalink

p.p.s. Jeffrey – I am not using geocoding plugin; just native LR. Is that the problem? I have a huge catalog and really don’t want to expand it with a parallel set of geodata, which is why I have not used your geo plugin…

My plugin doesn’t create parallel data (anymore… it did have to do that back in Lr2/Lr3 days). —Jeffrey

— comment by Roderick Laird on May 31st, 2015 at 11:52am JST (7 years ago) comment permalink

I get the following dialog every time I start Lightroom:
When I click OK I get prompted to give “Windows Command Processor” admin rights, presumably to install something. I allow it but get no visual feedback that anything actually happened.

OS: Windows 8.1 64-bit
Lightroom 6 (latest updates, but not CC) installed

Please see this FAQ. —Jeffrey

— comment by Henry Gessau on June 5th, 2015 at 10:50pm JST (7 years ago) comment permalink

Hi Jeff,
With Google’s recent changes to Photos (unlimited storage space), I have a question for the plugin. Will there be a future version where we get the choice between “High Quality” (Google reduces the photo size to 16MBP and their own jpg-quality) and “Original size” (full quality/the quality we set our photos to be uploaded)? Because only the “High Quality” setting does not count towards the storage space, e.g. they they free / unlimited.

Google has not exposed any of this to the PicasaWeb API, nor have they yet made an API for Photos. Hopefully they will (hopefully soon), but no word yet. —Jeffrey

— comment by Peter S on June 8th, 2015 at 7:06pm JST (7 years ago) comment permalink

I made some tests regarding using Google Photos with this plugin. I think that as long as I keep the file size to 16 megapixels it will not count against my limit.

However, there is a bug: The plugin currently prevents me from uploading videos larger then 100mb. This is no longer a limitation to Google:

I can actually upload videos as big as 10gb as long as they are still 1080p.

Can you please push a fix for this?


Unfortunately, it’s a limit for non-Google apps. See this FAQ. —Jeffrey

— comment by Oded Shopen on June 22nd, 2015 at 12:33am JST (6 years, 11 months ago) comment permalink

I am having continued and consistent UNAVAIL GumbyTask errors. They are specific to individual albums, as if that album has become corrupted. I keep trying to publish and I am unable to get any additional photos published. I’ve had this issue for at least several months now. I am using 20150612.281 of jf Picasaweb

I wish I had a solution, but as best I can figure out, this error is a Google back-end over-capacity kind of thing. I don’t know how they have their server farms set up, but it wouldn’t surprise me if an album gets assigned a farm at the time of creation. If that’s the case, and if they have capacity issues at a farm, you’d see this error with only those albums. But this is all speculation. In any case, I don’t have a solution… there’s not much anyone outside of Google can do about this. )-: —Jeffrey

— comment by barney on June 22nd, 2015 at 5:44am JST (6 years, 11 months ago) comment permalink

Hello Jeffrey,

I use your PicasaWeb plugin with great pleasure for quite some time now and I would like to thank you for it. Sadly I now encounter a problem with creating a new album. The plugin (Lightroom) gives me the following message:
“Create new album at PicasaWeb aborted: Unexpected HTTP status from Google: 500”
I have the latest plugin (20150621.281), run Lightroom CC 2015.1
Could this have something to do with Google switching to Google Photos?

best regards,

It’s just Google having “issues” on their back end. It’s been pretty rough for a while now. Not much we can do but wait for them to get their act together. —Jeffrey

— comment by Jeroen Kluft on July 29th, 2015 at 7:27pm JST (6 years, 10 months ago) comment permalink

When installing the Picasaweb plugin it doesn’t matter where I put it, it always tells me that the plugin can’t write its log file. No log will be maintained.

The log location is not related to where the plugin files are… Lightroom tells the plugin where your system temp folder is, and the plugin tries to create it in there. —Jeffrey

— comment by Kerim Razack on October 4th, 2015 at 12:38am JST (6 years, 8 months ago) comment permalink

I have totally had it with Google Photos. Today, I tried to upload photos with your plugin. I tried to create an album, which resulted in an error. I then went into Google directly, created the album, and tried to upload photos from your plugin and received 403 errors. This is a site for my camera club and I need to upload about 70 photos each month. I want to move the site to Flickr. Is there some way that I can use your Flickr plugin to access two accounts, mine and the one I want to start for the camera club? Thank you

My Flickr plugin can work with multiple accounts just fine… you choose the account when you export, or when you set up a Publish collection. But you won’t necessarily find things are better there… Flickr has been really Flaky lately, with lots of upload problems. Like with Google they come and go, and if you hit them, the only recourse is to wait and hope. —Jeffrey

— comment by Terry Straehley on October 9th, 2015 at 2:33am JST (6 years, 8 months ago) comment permalink

Hi Jeff.

Lightroom version: CC 2015.2.1 [ 1046594 ]
Windows 10 x64 Pro N
jf PicasaWeb 20150612.281

When exporting to Google with the ‘high quality’ option selected, Google fails to recognise the exported images are under the limit. If you click on an image in Google photos, it will report quota used as, for example, 16MB and then a split second later will recalc this to 0MB used. But Google won’t do this automatically. This means photos all use quota up regardless of the setting. Not sure why. If I export to HDD and upload the same images, it’s fine. Just thought you should know. No doubt a Google issue.


PS: Thanks for a great plugin.

They haven’t exposed any of this quota stuff to the third-party API that the plugin must use (there’s no “Photos” API… it’s all still through the old PicasaWeb API). Clearly this is not a priority for them, I suppose this is how it will be. —Jeffrey

— comment by Andrew on October 18th, 2015 at 11:24pm JST (6 years, 7 months ago) comment permalink

Would it be possible to have a setting to automatically create an album (or select it if it already exists) based on the directory name that the images are coming from? This way I would be able to save an export profile for picasaweb uploads. Currently it is mandatory that I visit the export dialog box and create an album prior to uploading. Thank you for all the hard work! I am a contributor, twice now!

Yes, you can do this via the “add/edit auto destination” link just below the list of albums in the Upload Destination dialog. The feature is used to similar effect in this blog post, so that should get you started… —Jeffrey

— comment by David on November 26th, 2015 at 9:06am JST (6 years, 6 months ago) comment permalink


Sorry for bad english but i’m French.

Please, can you developp possibilty to send picture automic in HIGH QUALITY (16Megapixel) OR ORIGINAL QUALITY? Because High Quality is free and unlimited in Google Photo.

In my Google Photo i say HIGH QUALITY but when i upload from LR with your plugin it say they are in ORINIGAL QUALITY and use my 15 Gb Free space google account.

Thank you for your work

Sorry, but Google does not allow this. They have no public API for Google Photos, so the plugin uses the (very old) API for PicasaWeb. It has no way to specify Google Photos settings like quality. )-: —Jeffrey

— comment by Alexandre on November 26th, 2015 at 11:23pm JST (6 years, 6 months ago) comment permalink

Using PicasaWeb Export ver. 2015.1215.284 with Lightroom 5.7.1. I can upload .rw2 files manually through the Picasa Web browser interface. However, when using the plug-in the final export dialog says “PicasaWeb does not accept “.rw2″ files for upload; aborting” when I try to use it. I am also blocked from uploading other types of RAW files such as “.cr2” and “.nef” with the plug-in. Is this a limitation of the API or can I get around this?

It’s an API limitation. The API has not been updated since before Google Plus was released, so it has no support for all the stuff added since then (e.g. Google Photos). If they ever release a new API I’m sure I’ll make a plugin for it, but considering it’s been so many years since Google Plus was released and there’s still no API, I wouldn’t hold my breath…. —Jeffrey

— comment by Paul Ott on December 27th, 2015 at 8:00am JST (6 years, 5 months ago) comment permalink

Hello from Canada,

After running out of Google storage space, I decided to come here to see if anyone had a solution to storing Original photos rather than High Quality photos when using this plugin to upload photos to Google Photos / PicasaWeb.

While it is very clear that so far Google has not provided a public API for storing the photos as High Quality (which does not count against your storage quota) verses Original (which does count against your storage quota), Google Photos web interface now provides a feature to post-convert ALL your Original photos to High Quality.

To see how much space you can recover, try the following:
1) Visit
2) Click the Recover Storage button

Performing this action does not impact photos uploaded via Google Drive.



— comment by EdQ on January 5th, 2016 at 7:35am JST (6 years, 5 months ago) comment permalink

Hi Jeffrey,

Just wondering if will be possible to log in to different google accounts-roots at the same time using this plugin.

Right now, using the browser, the user can be logged to several google accounts but the plug in only allows to configure just one root & account.

Working professionally is very common to have different accounts to upload pictures. They can be owned or from clients

Thanks for you great work and comprehension

Best regards,

Luis Muñoz

It’s unlikely, sorry. It’s easy to switch among users with the plugin, and each Publish Service can have a different user (so in that sense any number of users can be active at the same time), and for non-Publish exports the Google account is part of an Export Preset so you can make a preset per account… —Jeffrey

— comment by Luis Muñoz García on January 20th, 2016 at 8:16pm JST (6 years, 4 months ago) comment permalink

This is a suggested workaround in response to others’ questions about the “unlimited storage” option recently added to Google Photos.

Photos uploaded via the Picasaweb API (including via this plugin) will count toward your Google storage, regardless of whether you choose “high quality” compression in Google Photos. This has been discussed here and elsewhere.

To work around the issue, you can have Google re-compress your images after uploading them by using the button “Recover Storage” in the Google Photos settings page. Thanks to another Picasaweb user for finding this. The workaround has obvious limitations (2-step process, no persistent setting, requires available Google storage), and less obvious limitations (does not work for photos uploaded via Google Drive), but it may be sufficient for some folks’ purposes. It is for me.

— comment by DarthBrader on January 27th, 2016 at 3:15am JST (6 years, 4 months ago) comment permalink

Picasaweb is being discontinued as of May 1, 2016 (March 1, 2016 for Picasa desktop app). Hoping there will still be a way to export from Lightroom (5.7).

I have the impression that you’ll still be able to upload photos. If/when they release a Google Photos API, it will be #1 on my to-do list to make a plugin for it. —Jeffrey

— comment by John on February 13th, 2016 at 2:02pm JST (6 years, 3 months ago) comment permalink

Some info on deprecation of Picasa. Note the desktop app will not be supported after March 15, 2016

Info about changes to the Picasa Web Albums Data API

— comment by John on February 13th, 2016 at 2:08pm JST (6 years, 3 months ago) comment permalink

Jeffrey… I was using your pluggin years. I have close to 200 Albums. I realize now that I can upload full resolution all my pics now. Problem.. all my albums has been resized down to 1024 since storage was not unlimited before.. Is there any fast an easy way to change resolution to full (no resizing) for all albums that I already created and mantained on your PicasaWeb plug-inn estructure?. Plug-inn version 20151215,284. I write from Spain. Thanks a lot

BTW… I’m afraid of the lack of API support for your. I’m seriously thinking on moving to Flickr… any advise? Any way for migrate all my work to there?

Just edit the Publish Service and adjust the resize options to your liking. When you save the settings, Lightroom will ask whether you want to republish everything. Answer “yes” and do so, and the copies at PicasaWeb will be replaced with new copies. About migrating, I don’t know about tools at Flickr, sorry, you should check there. —Jeffrey

— comment by Alvaro on February 22nd, 2016 at 5:55am JST (6 years, 3 months ago) comment permalink

I can’t upload to PicasaWeb anymore. It used to work for years. I haven’t tried uploading in a few weeks, but now it’s failing. I tried erasing credentials and trying again but I can’t even authenticate now from the plugin. It just hangs.

I’m on the latest version on Mac.

What seems to be happening when it hangs? Are you sure there are no dialogs hidden behind another window somewhere? —Jeffrey

— comment by John M on February 23rd, 2016 at 2:05am JST (6 years, 3 months ago) comment permalink

Ah, i just saw the hidden window. Here’s the error:
Assert Failed picasaweb#284 +42513.2: [x7faed548cc98] @OAuth2 line 132:
Couldn’t authenticate: result in refreshAccessToken not a string:
[x7faed548cc98] @OAuth2 line 132
… [x7faed548cc98] @PicasaWeb line 108

The superficial problem here is that my plugin does not handle this situation gracefully, but the underlying situation is Google being flaky. Considering that they’ve been really flaky for the last year or so, and that they’ve announced the shutdown of PicasaWeb, I don’t have much hope that their error will be fixed, and I’m reticent to spend the energy to make the plugin respond more gracefully. Hopefully Google will release a Google Photos API and we can all move on to there… —Jeffery

— comment by John M on February 23rd, 2016 at 9:34am JST (6 years, 3 months ago) comment permalink

Hi Jeffery, thanks for the reply. I understand your frustration (I’m a software engineer as well).

However I ask you to please reconsider; this plugin is a core part of my workflow (and I’m sure others).


My updating the plugin to report this particular error more gracefully won’t solve the problem and get your workflow back on track… only Google fixing the underlying bug will do that. I have the impression that it comes and goes, so you might have better luck later. I also heard one report related to Google Drive… enabling (or disabling?) it made it work for someone, but I suspect that’s more coincidence than not. —Jeffrey

— comment by John M on February 24th, 2016 at 10:13am JST (6 years, 3 months ago) comment permalink

Hi Jeffrey: I’m planning seriously move from Picasa (now Google Photo) to Flickr. Seems like Google compress photos and videos (even if they are short or smaller than 16MP). Of course, the lack of support of your Lighroom pluggin is the final add to move to flickr. Problem: I already have 100 albums on Picasa, that would move to Flickr. Is there any way to do it smoothly?


Flickr may well have migration tools, but other than that guess I don’t know of an easy way, sorry. —Jeffrey

— comment by Alvaro Garcia on March 20th, 2016 at 8:30am JST (6 years, 2 months ago) comment permalink

Hi Jeffrey, I’m not sure if anyone posted about this or not. I just saw a notice on the Google Picasa-Web developers page that says on May 1 some of the existing functionality the API supports will be dropped. With that said, some features will continue. I just don’t know which ones your interface requires. Do you think the integration tool you created will stop working? Please let me know. Thank you!

Google’s message, copied from

“Important: Beginning May 1st, 2016, we’ll start rolling out changes to the Picasa Web Albums Data API and no longer support the following functionality:

*Flash support
*Community search
*Mutation operations other than uploads
*All support for tags, comments, and contacts
The API will still support other functions, including reading photos, reading albums, reading photos in albums, and uploading new photos. Although these operations will continue to be supported and the protocol will remain the same, the content included in the responses and the operation behavior may change. We’ll update the documentation on this site with specifics on the changes in March. Read other important Picasa updates here.”

If by “comments” they mean comments on photos, then that indeed will stop working with respect to published photos. Everything else should work… until it stops. Google has made it clear that they’re abandoning PicasaWeb. —Jeffrey

— comment by Rick Rajewski on April 27th, 2016 at 11:38pm JST (6 years ago) comment permalink

Hi Jeffrey,

I’m able to authenticate to my normal google account with your plugin (, but my google apps account (, grandfathered free plan) fails with a 404 unknown user. Anyone else running into this?


It’s not rare these days (see this FAQ), but I’m not sure whether it has anything to do with the “goodl apps” nature of the failing account. So far, it just seems to be random flakiness. —Jeffrey

— comment by Allie on August 7th, 2016 at 12:37am JST (5 years, 10 months ago) comment permalink

Update! After a long time of getting the 404 error, I went into my google apps admin interface, went to the google photos app, and re-selected “ON for everyone”. Note that this app was *already* “ON for everyone”. But, perhaps re-selecting this setting reset something inside of the googleplex… because I can now authenticate. Just wanted to report back in case anyone else was having a similar issue with google apps…

— comment by Allie on August 8th, 2016 at 6:00am JST (5 years, 10 months ago) comment permalink

Hi Jeffrey!

Thanks a bunch for this magnificent plugin. I’ve been using it for some years now on different machines and have always loved it. One thing I noticed recently though: when changing the star rating of an image, it reappears in the Republish section even though I unticked the box allowing the plugin to republish after a change to ratings (actually I unticked all the boxes just to be sure). I tried working with colours instead, but this makes the images pop up in Republish as well. Any workaround for this one? I’ve seen similar requests for changes to metadata where you explained this is actually a problem on Adobe’s side, but I kinda hope this is different (and therefore solvable!).

Thanks a lot for your great plugin!

If you’ve set things up in the “Metadata That Triggers Republish” section and it’s still not workin, then sorry, it’s not different…. still a bug in Lightroom. )-: —Jeffrey

— comment by Caenwyr on August 23rd, 2016 at 10:50pm JST (5 years, 9 months ago) comment permalink

Hi Jeffrey,

I tried the Picasaweb Plugin, works fine except for one thing:
Can I set somewhere that the uploaded images do not substract space from my Google Drive?

Greetings from Munich

No, sorry, Google does not allow 3rd-party uploaders like the plugin to do that; they require that you use their uploader for that. —Jeffrey

— comment by Adam on September 6th, 2016 at 1:24am JST (5 years, 9 months ago) comment permalink

Hi Jeffrey,

For my first series of photos only approximately 35 of the 364 total items that I was attempting to upload actually uploaded to Google Photos. I received this error message:

“Couldn’t render image: readNegative: dng_error_bad_format”

Can you help me get this to complete?


This is Lightroom’s cryptic way to say that your master image file is corrupt (or couldn’t be read well). —Jeffrey

— comment by Ben on September 27th, 2016 at 11:43pm JST (5 years, 8 months ago) comment permalink

Hello Jeffrey,

First of all, thank you for your work and making the plugins available for free.

I recently installed your PicasaWeb plugin in order to upload videos to Google Photos. The plugin works perfectly well with photos, however I’m struggling with MOV videos.

No matter if I choose H.264 (whatever quality) or use “original unedited file”, the videos never show up properly on Google Photos, they get stuck in “Your video will be ready soon” state. On the contrary, if I upload the same original video file via Google Photos’ own web uploader, they show up just fine. The MOV files are from iOS 10 Camera app.

Plugin version 20160620.285 (I wish I could copy paste the version from Lightroom instead of typing it;) Lightroom 6.7, macOS 10.11.6


Traditionally, Google has had different rules and different processing for their own apps than they give for third-party apps. I hadn’t heard of this issue before, but with them shutting down Picasa and PicasaWeb, and not having an API for Google Photos in all these years, I don’t suppose it surprises me. Unfortunately, it’s not worth looking into with the impending demise of PicasaWeb. Hopefully they’ll release a real API for Google Photos…. some day. —Jeffrey

— comment by Márton Salomváry on October 27th, 2016 at 10:08pm JST (5 years, 7 months ago) comment permalink

I have what Google calls a “Brand Account” which somehow seems to under – or contained within – my normal personal account. I use the brand account for my photography business. My problem is that I can’t seem to figure out how to use your Picassaweb Publish Service plug-in to associate with this “brand account” . I already have your plug in set up to manage my personal account photos and want to keep that intact. How do I add a new Publish Service that points to the Brand Account?

Thanks — Dan

I’m afraid that I’ve never heard of a “Brand Account”, and can find no mention of it in PicasaWeb docs. They’ve let all this photo stuff wither on the vine, so it wouldn’t surprise me to find that it’s simply not possible. But who knows. )-: —Jeffrey

— comment by Dan (California) on November 21st, 2016 at 7:04am JST (5 years, 6 months ago) comment permalink

Hi Jeffrey – your PicasaWeb plugin is simply fantastic for my LR publishing needs to Google Photos. Everything is great except for one issue I’ve observed. If I have a photo that is added to multiple collections/albums, I find your plug-in will upload the photo multiple times to Google Photos – as opposed to linking to the album from an existing uploaded photo. Until Google Photos provide a way to merge duplicates on their server, is it possible to implement a duplicated check prior to the upload? Unfortunately, I often need to share the same set of photos with multiple groups (with some tailoring to each group), I’m getting a large amount of duplicates on Google Photos. Please kindly advise.


Even if the PicasaWeb API supported it, it would be really difficult to shoe-horn into Lightroom’s Publish paradigm, and since Google has abandoned PicasaWeb, so I’m reticent to put any more resources into it. Let’s just hope they come out with a Photos API this century. /-: —Jeffrey

— comment by Ron Chan on January 15th, 2017 at 3:40am JST (5 years, 4 months ago) comment permalink

Hi Jeffrey
Lightroom cc latest version Picasa plugin latest version. macOS
Not used plugin for some time so needed to re register and allow plugin in google – getting the following error message

unrecoverable server error at Google it returned a normal web page instead the proper API reply

have logged out of Lightroom and restarted mac without any change

Please help

Kelvin from North West UK

I’ve just updated with a workaround… it should be working again if you update to the latest version of the plugin. No guarantee that Google won’t break things again soon, though. )-: —Jeffrey

— comment by Kelvin on January 27th, 2017 at 8:13pm JST (5 years, 4 months ago) comment permalink

Do you know if the picasaweb API has shutdown? I’m unable to upload pictures.


I’ve just updated with a workaround… it should be working again if you update to the latest version of the plugin. No guarantee that Google won’t break things again soon, though. )-: —Jeffrey

— comment by Guillermo on January 28th, 2017 at 5:54am JST (5 years, 4 months ago) comment permalink


Thanks for the replies to the comments above, I thought the problem was on my end for a day or so!

If I understand things correctly, you don’t have any ability to provide a workaround until Google supplies you with a Photos API? i.e. the picasaweb LR plugin is most likely permanently dead?



I’ve just updated with a workaround… it should be working again if you update to the latest version of the plugin. No guarantee that Google won’t break things again soon, though. )-: —Jeffrey

— comment by Jason Griffith on January 29th, 2017 at 3:58am JST (5 years, 4 months ago) comment permalink

Is this the API that isn’t working currently?

Yeah. But it turns out that parts are still working… I’ve updated the plugin to avoid what seems to no longer work, so if you update to the lastest version, it should work again. —Jeffrey

— comment by Doug on January 29th, 2017 at 6:27am JST (5 years, 4 months ago) comment permalink

This maybe relevant from another plugin:
Thanks for the pointer. Rob Jones of New P Products got back to me with info on a workaround. My plugin now works again….. until Google next breaks it, at least.—Jeffrey

— comment by Doug on January 29th, 2017 at 7:50am JST (5 years, 4 months ago) comment permalink


From today it seems the PIcasa plugin doesn’t work anymore.
I always receive a network error

Neither upload a new album nor update an existing one.

Best regards,

P.S: Thanks for your great plugins!

I’ve just updated with a workaround… it should be working again if you update to the latest version of the plugin.—Jeffrey

— comment by Olivier Hollender on January 30th, 2017 at 4:55am JST (5 years, 4 months ago) comment permalink

Hi Jeffrey!

Thank you – it work’s excellent again!

Best regards, Arnold

— comment by Arnold Lengauer on January 30th, 2017 at 9:23pm JST (5 years, 4 months ago) comment permalink

Thanks for the quick fix !
Glad to see that there is cooperation between “concurrents” in such cases !

JC from France

— comment by Jean-Claude on January 31st, 2017 at 5:10am JST (5 years, 4 months ago) comment permalink

Hi Jeffrey,
Thanks a lot for the update, you save my day!

— comment by Olivier Hollender on February 1st, 2017 at 3:01pm JST (5 years, 4 months ago) comment permalink

Hello, great plugin! I have noticed a Google 501 Update No Longer Supported error this evening. I am using Mac OS 10.11.6, Lightroom CC, and plugin version 20170130.288. Is this the end of the plugin as supported for Google Photos currently?

It’s still working for me at the moment, but I’m getting many reports of the “Update No Longer Supported”, so the writing seems to be on the wall. —Jeffrey

— comment by Noah on February 8th, 2017 at 4:03pm JST (5 years, 4 months ago) comment permalink

Hi Jeffrey,

Firstly, thanks for the awesome plugin – have been using for years and has been a key piece in completing my LR workflow.

Last night a new issue started popping up. After clicking publish with at least 1 new photo, a dialog box appears saying:
“Unexpected HTTP status from Google: 501
Update is no longer supported”

What’s strange is that if you have multiple images to publish, this message will appear, and after dismissing, it will seem like the publish action failed completely, with no images uploaded. However, in the album on Google Photos, the first image that was to be published will have been uploaded. If you then try and click Publish again, exactly the same happens, but a duplicate of that first image is added the collection (I had tried running publish a few times before checking the album, at which point there were 4 of the same image uploaded, but nothing else).

Let me know if you need any other recreation steps.



Lots of folks are getting this error (though I’m not yet). I think the writing is on the wall that they’re starting to wind down the service. —Jeffrey

— comment by Michael Shannon on February 9th, 2017 at 3:31am JST (5 years, 4 months ago) comment permalink

Hi Jeffrey,
I have been using your plugin successfully for a few years now but it has now stopped working.

I am using IOS 10.12.1, lightroom CC 2015.8 and your plugin ending .288

The screen message says no longer supported

Are you able to help please.


Google is shutting down PicasaWeb and abandoning photographers. —Jeffrey

— comment by john seaman on February 13th, 2017 at 10:37pm JST (5 years, 3 months ago) comment permalink


I am using your great plug on Light Room 5 for log time with no issues.

Effective last week I was unable to upload photos to Picasa.
I keep getting LR message – “Unexpected HTTP status from Google:501, insert no longer supported.
I updated to latest JF release – 20170130.288. Same, same.

When pressing PUBLISH – I get “Catalog Corruption Discovered” window with the message: Missing destination cookies.

I deleted all items from JF and selected just few catalog items for testing – Same same.

Also double check that Google does “know” JF and that it is enabled. No success.

Please support…


Google is shutting down PicasaWeb, so many things don’t work anymore. The “catalog corruption” is unrelated, but not worth fixing because PicsaWeb won’t work anymore anyway. —Jeffrey

— comment by Zvi Segal on February 15th, 2017 at 2:05am JST (5 years, 3 months ago) comment permalink

I was wondering if you know of any google photos product forum post, or some place with a feature request for API uploads.. Just some place one can vent the frustration that picasaweb API was killed without any replacement..
I did a quick google search but haven’t found anything..

also you don’t by any chance know a useful workaround? 🙁 Not having my DSLR photos right next to my Smartphone photos on Google Photos makes it so much less powerful.. (Not your problem, but I guess people here are in a similar position)

thanks for your continued effort and great export plugins!

There’s a PicasaWeb developer forum, but Google’s participation is limited to occasionally stopping by to rub salt in the wounds and dazzle with their indifference. —Jeffrey

— comment by Herbert Poul on February 19th, 2017 at 2:20am JST (5 years, 3 months ago) comment permalink

I know about the trouble with Picasa, but the upload API is still working. Picasa photo upload and other tools can still upload. I think google will keep an upload on the long run. So why not fix the current issue?

I’m not sure what you mean by “current issue”… Google is shutting things down. Even uploads fail for some folks. —Jeffrey

— comment by Tires on March 28th, 2017 at 6:25am JST (5 years, 2 months ago) comment permalink

Hi Jeffrey… using your Flickr plugin for quite some time. Great product – happy customer 😉

I’m on macOS 10.12.4, your newest plugin 20170309.391 and Lightroom 2015.9, and yesterday a weird thing started: On export the geolocation seems to get shuffled with locations from other images I’ve taken elsewhere. Eg is in Augsburg, Germany – another photo from the same export is in Bad Blumau, Austria, a third one in Al Ain, UAE. All locations are correct in Lightroom: Goa, India.

What’s hapenning?

The rest of the exported metadata is correct, eg tags or titles. I changed those to test if the photos are correctly linked to my catalog. All fine except the geolocations 🙁

Thanks for your support!

That’s really weird. Could you try sending a plugin log after and upload that wanders? Thanks. —Jeffrey

— comment by Harald Felgner on April 17th, 2017 at 10:53pm JST (5 years, 1 month ago) comment permalink

Jeffrey I can no longer upload from Lightroom CC to my Picassa Albums. Can you suggest how to move my images somewhere else and maybe a place to move them. Many thanks as I have enjoyed this plugin so much and appreciate you maintaining it. I am from Choctaw Oklahoma USA and a freelance photographer.

Where to move them depends on what’s important to you. Lots of places are free or offer free trials, so give them a try, such as Flickr, Zenfolio, or SmugMug. Some places allow you to import from other places, or maybe just re-send from Lightroom. I don’t really have experience here, so can’t suggest much more. —Jeffrey

— comment by Tom Caton on August 4th, 2017 at 3:44am JST (4 years, 10 months ago) comment permalink

Hi Jeffrey,

I’ve successfully and happily used your Export to Picasweb plug-in as long as Google allowed. I appreciate your effort and splendid code, but after having googled every other week for a solution to revitalize the excellent solution, I (with the rest of the community) have to find another solution.

Before moving on, I would very much like to convert all collections I’ve made in jfPicasaweb into LR’s own collections. Dragging them is to no avail.

Do you happen to know how to convert the collections?

One way would be to use my Data Explorer plugin, selecting all the collections and invoking the data-explorer plugin and having it report on all Publish Collections any selected photo is part of. In the result dialog, you can click on the “isolate” button next to each one you’d like to see as a normal collection, and the plugin will create it. You can then go move them around and rename them as you like. —Jeffrey

— comment by Ståle Freyer on August 8th, 2017 at 8:15am JST (4 years, 10 months ago) comment permalink

I have been using Picasa Web for a LONG time, using your publish service mostly. I no longer use Picasa for uploading anything new, but I still have a large number of galleries still linked to my photos in Lightroom.
Now I am running into a big problem- As I go through my old collection of photos in attempt to delete anything I no longer need, I occasionally get this message when attempting to delete photos-
“The plugin’s authorization for your PicasaWeb account has expired… please visit the top of the Export Dialog to re-authorize the plugin for your PicasaWeb account.”
This leaves me unable to delete the photos. I have tried re-authorizing to no avail. I have tried removing photos from the publish collection galleries and that does not work either.

Do you know of any workaround that will allow me to delete photos?

Thanks in advance for any suggestions you may offer.

In the Publishing Manager for the Picasaweb plugin, there’s a section on delete options. Adjust that so that photos deleted from Lightroom are not deleted on Picasaweb, and hopefully it should work. You can also disable the plugin in the Plugin Manager. —Jeffrey

— comment by Jeremiah Toller on August 20th, 2017 at 5:21am JST (4 years, 9 months ago) comment permalink

Love your work and have bought a few plugins in the past (zenfolio, folder publisher). A question on the Google Photos plugin development. You mentioned that Google won’t release APIs. I found a post with a developer saying that he developed a plugin for Google Photos. How does this work and what is different from your plugins for other services?

It uses the same now-deprecated PicasaWeb APIs as my PicasaWeb plugin, so I doubt it works anymore, at least, not reliably. —Jeffrey

— comment by Magnus on November 9th, 2017 at 12:53am JST (4 years, 7 months ago) comment permalink

FWIW, I have now tried the Google Drive export plugin since there is now an option in the Google Photos Settings “Show Google Drive photos & videos in your Photos library”. It seems to work quite well so far. All Photos show up in the right place in Google Photos, only Videos have the wrong time stamp, but even updates to photos seem to work just as expected. Unfortunately the Keywords are ignored, but other than that I can see not too many downsides (except that it’ll probably count toward your storage limit)

— comment by Herbert Poul on December 9th, 2017 at 5:03pm JST (4 years, 6 months ago) comment permalink

There is a new API for Google Photos, check this out:

Yes, thanks, I’ve already started working on a plugin. The new API is not ready for prime time yet, though… it’s still extremely limited in what it allows, and what it does allow doesn’t always work correctly. But at least it’s a step in the right direction… —Jeffrey

— comment by Juan Pedro on May 13th, 2018 at 10:54pm JST (4 years ago) comment permalink

Hi Jeffrey!

Google introudeced the Google Photos Library API:
Are you planning to create an export6publish pugin to Google Photos?


— comment by Zoltán Tóth on May 29th, 2018 at 7:18am JST (4 years ago) comment permalink

I think Google released the Google Photos API:

If you’re planning to update the plugin please check the possibilty to auto create albums inside Lightroom that reflects on Google Photos.

Thank you!

I’ve been working on a plugin with it for a while, but it (their new API) is not powerful enough yet, so we have to wait a bit longer…. —Jeffrey

— comment by vynnus on May 30th, 2018 at 8:37am JST (4 years ago) comment permalink
Leave a comment...

See the known issues before reporting bugs. Also, when reporting bugs, please include the OS, the version number of Lightroom, and the version number of the plugin. PLEASE REPORT THE NAME AND FULL VERSION NUMBER OF THE PLUGIN WITH EVERY REPORT. Seriously. I need the full version number or I likely can't do anything but ignore the message.

All comments are invisible to others until Jeffrey approves them.

Please mention what part of the world you're writing from, if you don't mind. It's always interesting to see where people are visiting from.

You can use basic HTML; be sure to close tags properly.

Subscribe without commenting