Sometimes problems do occur so please get in contact by adding a comment at the bottom of this page and I’ll do my best to try and help. Please remember to use a real email address when you post a comment so that I can get in contact if necessary (your email address will not be visible publicly).


Latest support news

11 Feb 2024 – Google Drive folder restrictions

Starting with version 5.9.6, the Photo Upload plug-in no longer lists Google Drive folders that it has not created itself, including shared folders and shared drives. All the upload capabilities still exist, but any folder that has not been created by the plug-in is not visible and cannot be uploaded to.

Google have announced that the Photo Upload plug-in can no longer access any folder or file that the plug-in has not created itself, including shared folders and shared drives. I’ve done my best to try and persuade the Google app verification team that accessing these folders is very useful to people uploading their photos to Google Drive, but Google have not been flexible on enforcing the new restrictions.

29 Jul 2022 – Uploading to Amazon Drive ending on 31 Jan 2023

Amazon have announced that they have deprecated Amazon Drive and are ending it on 31 Dec 2023 and preventing new files being uploading to it on 31 Jan 2023. This plug-in uses Amazon Drive to upload photos such that they can be viewed in Amazon Photos. On the date that Amazon prevents the plug-in uploading files to Amazon Drive this plug-in will no longer support uploading photos to Amazon. Unfortunately Amazon have not provided an alternative approach for apps such as this plug-in. The future approach for uploading photos to Amazon Photos after Jan 2023 is therefore going to be via the Amazon website or Amazon’s own apps.

6 Feb 2022 – Publishing and exporting hangs after one photo

With Lightroom 11.2, Adobe introduced a bug that causes publishing and exporting to hang after one upload. This has been reported here:

There seems to be one solution which involves clicking on a different collection when the publish/export first appears to hang. The second solution is simply to re-install Lightroom Classic 11.1 instead of 11.2.

Hopefully Adobe will fix this in the next update for Lightroom.

Update 12 Apr 2022 – Adobe report they have fixed (in Lightroom Classic 11.3) the hanging when publishing a collection.

18 Oct 2020 – Pinterest no longer authenticates

Photo Upload no longer authenticates with Pinterest and cannot currently be used to upload photos to Pinterest. It seems that Pinterest have disabled the API that the plug-in uses to communicate with Pinterest.

Photo Upload uses v1 of the API from Pinterest and has been an approved app by Pinterest since 2015 (it went through their approval process). Pinterest announced on their developer website sometime in early 2020 that there was a new v2 API available.

On 17 Apr 2020 the Photo Upload plug-in applied to use the v2 API.

On 5 Aug 2020 Pinterest sent me a notification that “the current version of the Pinterest Developer API will be deprecated in three months, on O‌ctober 3‌1, 2‌020.

Note: Deprecation does not mean “removed”, but I think in this instance Pinterest actually meant to use the word “disabled”. The word “deprecation” is used to announce that something will be removed in the future.

Pinterest asked that apps apply for the v2 API. I contacted Pinterest saying that the app had applied for the v2 API back in Apr.

On 31 Aug 2020 Pinterest sent me this reply: “Unfortunately, this is no ETA when the new apps will be approved as I have mentioned we are a very small team and currently experiencing a large backlog of applications. We’re working as fast as we can to review and get back to everyone and also we do not prioritize requests for any users as of now. I hope this clarifies.

On 18 Oct (or perhaps a few days earlier) Pinterest disabled the v1 API and the Photo Upload plug-in stopped working. Clearly this was before the 31 Oct date that they previously announced the API would be “deprecated” on.

I’ve emailed the developer support at Pinterest again and again over the past 6 months.

On 26 Oct I received the latest reply from them: “I can totally sense the trouble you’re experiencing on your end and I apologize for that. However, we’re bounded with limitations on our end. As I mentioned earlier, the requests for the app are getting reviewed by our internal team. I too agree that it has taken a longer time than expected. But please be assured as I’ve forwarded your feedback to our team. And, I’m sure they will look into your concern and get back to you at the earliest.

Unfortunately there is nothing more I can do to encourage Pinterest to grant Photo Upload access to the v2 API. Pinterest disabled the v1 API earlier than they said they would (was meant to be 31 Oct). The whole idea of a deprecation cycle is to give developers time to move to a new way of doing things (i.e. v1 to v2) but in this case they have not processed applications after 6 months! Hopefully you can see that I’m very frustrated by this, I actually haven’t worked with a less professional mainstream organization with the Photo Upload plug-in.

At this stage I’m waiting to hear from Pinterest about whether they will grant the plug-in access to the v2 API. But I’ve been waiting more than 6 months…

Update 17 Nov 2020 – Pinterest finally granted the Photo Upload plug-in access to their latest Pinterest API and the plug-in has been updated to support it.

6 Sep 2018 – Picasa Web retires on 15 Mar 2019

Google have announced that the Picasa Web interface used by the Photo Upload plug-in is retired on 15 Mar 2019. The plug-in stops working with Picasa Web at that time.

The Photo Upload plug-in now has the Google Photos service available to it (introduced in version 5.0.9 in Sep 2018), which uses the new Google Photos interface instead of the old Picasa Web interface.

The Google Photos support in the plug-in has been written from scratch and is quite different to that previously included for Picasa Web. You can purchase a license key for the Google Photos service in this plug-in from the usual places. Unfortunately, due to the time and effort needed to create the new Google Photos support in the plug-in, there is no free transfer or discount when moving from Picasa Web to Google Photos.

There are some differences between the new Google Photos interface and the old Picasa Web interface. Most notably you can now use the plug-in to create albums on Google Photos, but note that Google only allows you to upload photos to albums created by this plug-in (i.e. you cannot upload to albums that you already have on Google Photos).

20 Jul 2018 – Facebook prevents plug-in from being authorised

Facebook, in light of the Cambridge Analytica scandal, have prevented small businesses like this one from connecting to Facebook. The official date for this dropping of support was supposed to be 1 Aug 2018, but they seem to have taken action a little earlier.

Facebook have not responded to any requests for clarification on their policy for preventing small business access. Unfortunately at this time there is nothing else that can be said except that Facebook have prevented the plug-in from being authorised and therefore have prevented the uploading of photos using the plug-in.

This change of policy from Facebook is very much related to the inability to run Lightroom’s built in Facebook plug-in any longer. This is the warning message from Adobe that Lightroom now gives you for their Facebook plug-in:

15 Jun 2018 – 500px no longer supports plug-ins

500px have announced that as of this date they will no longer support plug-ins like Photo Upload to access their site. This is a decision made by 500px and not by the plug-in.

There is no alternative plug-in available for uploading to 500x from Lightroom.

If this decision affects you then please contact 500px directly and mention that you use or rely on the Photo Upload plug-in for Lightroom. I have also contacted 500px.

24 Apr 2018 – Facebook prevents plug-in from creating posts on user timelines

Facebook have announced that on 1 Aug 2018 they are removing the ability for third party applications to create posts on user timelines. Facebook are still allowing posts to be created for Facebook pages.

Specifically, Facebook have prevented applications from being granted a permission called “publish_actions” that allows posts to be created on user timelines.

Update 20 Jul 2018 – Refer to the news on Facebook dated 20 Jul 2018 above.

23 Jan 2018 – Picasa Web uploads fail (“500” error)

The Picasa Web API that 3rd party apps use to upload and manage photos for Google Photos is giving an error when uploading photos. The error from Google simply says “Internal error, try again later”.

Many other people and apps have reported the same errors, for example see this thread (which has nothing to do with this plug-in).

There are no indications from Google that this is either a planned outage or a planned change, so at this time I have to assume that Google will fix the problem sooner than later. I will keep an eye on the situation over the next day or so, but there is nothing else I can do at this time.

Please be aware that that 12 months ago Google made it clear that Picasa Web was being retired and no longer developed. Sadly, Google do not allow 3rd party plug-ins to upload directly to Google Photos (they can only upload to Picasa Web). My suggestion is that it is time to start looking at alternative photo sites if you want to upload directly from Lightroom.

Update 25 Jan 2018 – Google have now fixed the problem and Picasa Web uploads work again.

27 Feb 2017 – SmugMug no longer allows photos to be uploaded to “Private” galleries

SmugMug have prevented photos from being uploaded to galleries that have their visibility set as “Private”.

I don’t know their rationale why and I even asked them why in their support forum, but no reply – I’m not sure if SmugMug will fix this or if it is permanent.

You need to change the gallery visibility to “Public” or “Unlisted” then the upload should work.

Update 28 Jun 2017 – this is now fixed in plug-in version 4.5.7.

7 Feb 2017 – Picasa Web changes (e.g. albums cannot be created)

The Picasa Web API that 3rd party apps use to upload and manage photos for Google Photos has been updated by Google to prevent many update operations.

Google have now prevented the Picasa Web service from creating, renaming and deleting albums and from updating or deleting photos. If you are technically minded, please refer to this Google site for more information (see section titled “Mutation support removed”).

You can still upload photos using the latest version of the Photo Upload plug-in, and you can use the Google Photos website to create your albums before or after uploading to them from Lightroom.

Update 6 Sep 2018 – Google have released an official interface to Google Photos and this plug-in has been updated to support this interface. Please refer to the “Google Photos” service added to Photo Upload version 5.0.9. Google have announced that the old Picasa Web interfaces will be retired in Mar 2019.

Google Photos “shared albums”

Please note that Google does not tell the Picasa Web plug-in about any albums you initially create on Google Photos as “shared albums”. To work around this, please initially create albums on Google Photos as regular “albums” and then configure these to be shared albums afterwards.

7 Feb 2017 – Picasa Web uploads fail (“501” error)

The Picasa Web API that 3rd party apps use to upload and manage photos for Google Photos has been updated by Google to prevent many update operations. Older versions of the plug-in will display “501” errors from Google when trying to perform certain tasks like creating albums.

The Photo Upload plug-in has been updated with version 4.1.9 to handle these Google changes with “friendly” error messages. You should update your plug-in to 4.1.9 or later.

Please also refer to the note above on “Google Photos (Picasa Web) no longer allow albums to be created”.

Update 8 Feb 2017 – this is now fixed in Photo Upload version 4.1.9.

27 Jan 2017 – Picasa Web uploads fail (“400” error)

The Picasa Web API that 3rd party apps use to upload photos to Google Photos is reporting a “400” error with the message “Bad request”. This will affect all 3rd party apps that upload pictures using the Picasa Web API to Google Photos. There is a thread on the Google forums that is discussing the problem.

It is not known what causes the problem and when Google will fix the issue. I’d expect them to fix it quite quickly given the number of 3rd party apps that make use of uploading photos in this manner. I’ll track Google’s response – hopefully it will be quick and positive.

Update 28 Jan 2017 – this is now fixed in Photo Upload version 4.1.6. There has been no indication from Google what the problem is, but I’ve found an alternate way to upload the photos which appears to work well.

19 Apr 2016 – Facebook authentication fails

Facebook have mandated a few changes to authentication and old versions of the plug-in will receive a “URL blocked” message from Facebook when authenticating.

Update 19 Apr 2016 – this is now fixed in Photo Upload version 4.1.9.

16 Feb 2016 – Google announce changes to Picasa Web

Google recently announced that they will be making changes to the Picasa Web API that the Photo Upload for Picasa Web plug-in uses.

Google have been unclear about all the implications of these changes to applications such as the Photo Upload plug-in. However they have stated that changes to their API will not be made until 1 May 2016.

Google may keep the old Picasa Web API working, with some small changes or limitations. They may replace the API with a new alternative that the Photo Upload plug-in can use. Or they may do something else such as improve Google Drive integration for Google Photos, or remove third party API access to Google Photos entirely.

Google have noted that they will announce in March 2016 what the changes will be in detail, so until that time it is not possible to comment further on how Google’s plans will affect Photo Upload for Picasa Web.

Every effort will be made to ensure Photo Upload continues being able to upload your photos to Google Photos. When Google share more details of their plans then this news section will be updated with what this means for the Photo Upload plug-in. Until then, I’m afraid we have to be patient…

13 Nov 2015 – Lightroom hangs/freezes when closing

A few people have highlighted that Lightroom can hang/freeze when it is closing. Lightroom must then be force closed to make it quit properly. In some circumstances a window is shown during the hang that shows the Photo Upload plug-in is shutting down.

It appears that this is a problem with Lightroom, not with the Photo Upload plug-in. Please refer to this feedback page on the Lightroom forums:

The advice that seems to work fairly reliably is:

Reset the preferences (holding down SHIFT and ALT and starting Lightroom) and choose YES.

7 Oct 2015 – Zenfolio communication fails

During some scheduled maintenance on 6 or 7 Oct 2015 Zenfolio have changed the way security for internet communication is handled on their servers.

Update 7 Oct 2015 – this is now fixed in plug-in version 3.2.1.

31 Jul 2014 Old “Picasa Web Upload” plug-in replaced by “Photo Upload”

The old “Picasa Web Upload” plug-in originally launched in 2012 has been replaced by the “Photo Upload” plug-in which allows you to upload to Picasa Web and many other services.

The final version of the “Picasa Web Upload” plug-in is 1.5.8. If you have a version of the old Picasa Web Upload plug-in then please note that it is not possible to use it with Lightroom 7.0 or later. Instead please download the latest Photo Upload plug-in from this website. You can use your existing Picasa Web Upload plug-in license key with the Photo Upload plug-in’s Picasa Web service.

27 Jun 2014 – Flickr authentication fails

Flickr have changed the way authentication is handled on their servers.

Update 30 Jun 2014 – this is now fixed in plug-in version 1.7.9.


Updating the plug-in – always check you have the latest

If you think you have a problem, in particular if you think you’ve found a bug, then please make sure you have the latest version of the plug-in.

Use the Update button in the plug-in’s settings from Lightroom Plug-in Manager to check that you have the latest.

Update the plug-in from Lightroom Plug-in Manager

Downloaded plug-in from Adobe’s website and I have a ZXP file…

If you download the plug-in from Adobe’s Add-ons website then you will get a ZXP file. This type of file is intended to be opened by Adobe Creative Cloud (and Adobe Extension Manager.) If you don’t have Adobe Creative Cloud then you cannot do much with the ZXP file.

Adobe’s add-on installation process for Lightroom plug-ins is really quite complicated – and certainly convoluted.

My recommendation for a more straightforward install is to download the plug-in directly from this website. This will be a regular ZIP file rather than a proprietary Adobe ZXP file. And then simply follow the tried and tested installation instructions also on this website.

Lightroom reports “An error occurred while attempting to load this plug-in.

When using Lightroom Plug-in Manager to Add a new plug-in, you may get an error reporting “An error occurred while attempting load this plug-in.“. This error normally means the plug-in folder has not been extracted correctly from the downloaded Zip file.

Support - Plug-in Manager - Incorrect folder

Lightroom expects all plug-ins to have a folder extension of “.lrplugin” or “.lrdevplugin”. When you download a plug-in Zip file from this website, the top-level in the Zip file will be a folder ending in “.lrplugin”, e.g. “photoupload.lrplugin”. You must extract this folder itself, not just the files within it. Once you’ve extracted the plug-in folder from the Zip, you can move it around your computer (e.g. to your Documents folder) but you must not rename the plug-in folder.

Missing plug-in – The “nil” plug-in is not installed

Lightroom indicates that the plug-in is missing or shows the message “The “nil” plug-in is not installed” if it cannot find the plug-in folder on your computer that you used when you added the plug-in to Lightroom.

After using Lightroom’s Plug-in Manager to add the plug-in to Lightroom, you must not remove the plug-in folder. Lightroom needs to load the plug-in from this folder each time it starts.

If you get this message, please re-install the plug-in by following the installation instructions.

Authentication problem – Error authenticating with [service]

Support - Firewall

When trying to authenticate you may get an error such as this:

Photo Upload: Error authenticating with [service]
No authentication information returned from [service].

The common answer to this is that you are running a firewall (e.g. Little Snitch etc.) and have restrictions on the plug-in’s network access.

Consider whether you currently have network problems or are running a restrictive firewall.

Most firewalls identify this plug-in’s network access as coming from “curl” rather than “Lightroom”. Please make sure your firewall permits network access for the “curl” application.

You can use the “Test Connection” window to test whether your internet connection is working for the plug-in. You can find the “Test Connection” window within the “Configuration” window under the plug-in’s Setting section in Lightroom’s Plug-in Manager.

What is the Export Location used for?

Lightroom provides a setting for the plug-in called “Export Location”. This allows you to specify where Lightroom should create the copy of each photo that you are exporting. Lightroom creates a copy for each photo according to your edits and settings. For example, if you’ve cropped your photo and want to export it as a JPEG then this is what the copy will consist of.

I recommend leaving the “Export Location” setting as the default which is “Temporary folder”. This means that the copy of the exported photos will be removed once they have actually been exported.

Lightroom says my computer is out of disk space

Now that online storage is cheap or even free, people want to upload their entire photo collection.

Some people are finding out that when exporting a large number of photos and videos that Lightroom reports that their computer is out of disk space. This problem typically occurs more frequently on systems that have smaller hard disks, e.g. those with 256GB or less SSDs.

At the start of a publish/export process Lightroom starts creating copies of each photo that you are uploading according to the publish/export settings you have specified. Lightroom does this in parallel to the actual uploading being done by the plug-in and does not wait for the plug-in to request each photo copy. Lightroom does not allow the plug-in to dictate when the photo copies are made and when they are deleted.

The out of disk space problem occurs because Lightroom creates all the photo copies at the start of the upload and only deletes the copies when the plug-in has finished uploading the final photo. The photo copies are created in the computer’s temp folder (on a Windows machine this is usually on the same drive as the main Windows installation, e.g. drive C:). You will need enough space in your temp folder (and drive) to allow Lightroom to create publish\export copies of all the photos that you are uploading in one operation. The space used by Lightroom during the upload will be freed up once the upload has finished.

e.g. If each exported photo that is generated by Lightroom is 5MB in size, and you are exporting 1,000 photos then you will need 5GB of free space in the temp folder on your computer.

Note: Work arounds for this Lightroom problem are 1) use the plug-in’s “Generate exports one at a time” setting or 2) use the Configuration setting “Temporary folder for exported photos” to override where the temp folder is.

For reference, here is how you can find out where your system temporary folder is that Lightroom will be using for the temporary files during an export/publish:


  • Open Command Prompt
  • Type:
echo %temp%


  • Open Terminal
  • Type:
echo $TMPDIR

Location information not being uploading

Various online services (e.g. Google Photos) can make use of the photo location information in the photo’s metadata. If the location information is not being uploaded then check that you have enabled location information in Lightroom’s Export/Publishing Manager windows, i.e. you do not have “Remove Location Info” checked.

Old versions of Photo Upload for OneDrive (and the previous SkyDrive Upload) cannot be authenticated

Update your Photo Upload plug-in to a newer version (version 2.3.7 or later).

Microsoft appear to have changed something on their servers which requires an updated Photo Upload plug-in.

Use the Update button for the Photo Upload plug-in in Lightroom’s Plug-in Manager to get the latest version.

Note: If you are still using the old SkyDrive Upload plug-in then please take this opportunity to upgrade to the Photo Upload plug-in (your existing license key will still work).

WordPress self-hosted sites

The Photo Upload plug-in works with blogs hosted on and blogs that are self-hosted.

Authentication is always managed by, so you will need an account on even if you do not have a site hosted there.

  1. Create an account on (if you don’t have one already). This is free, you do not need to create a site on
  2. Install the Jetpack plug-in on your own self-hosted WordPress site (
  3. After the Jetpack plug-in is installed, connect it to your account (
  4. Log in to using your account and add your own self-hosted WordPress site (e.g. or personal domain) to your account
  5. In the Photo Upload plug-in in Lightroom, use the Add/Refresh button to authenticate the plug-in with any of the sites registered with your account

For self-hosted sites, you will need the Jetpack WordPress plug-in on your WordPress site. Ensure that you have version 3.1 or later of Jetpack installed. Version 3.0.2 of Jetpack had an error that prevented authentication. This Jetpack error was fixed in 3.1.

The plug-in cannot be authenticated with sites hosted locally at “localhost”. Authentication needs your WordPress site to be registered and accessible by WordPress does not allow such local sites to be registered.

WordPress blog site selection

WordPress allows you register multiple blogs with your account. You can select from your available sites using the drop down list in your Web brower when authenticating the plug-in with WordPress.

Photo Upload (WordPress) authentication with WordPress

WordPress authentication does not return an authentication code

Sometimes WordPress plug-ins can prevent the Lightroom plug-in from authenticating with your site. These plug-ins prevent you receiving an authentication from WordPress, i.e. the page with the authentication code does not open in your browser.

The problematic WordPress plug-ins tend to be security ones. There are known issues with these WordPress plug-ins, but other security plug-ins are likely to interfere with authentication too:

  • All In One WP Security
  • iThemes Security Pro

If you do not receive an authentication code in your browser please disable the security plug-ins and try the authentication again. You should be able to re-enable the plug-ins after the authentication has successfully taken place.

Plug-in not compatible with your version of Lightroom

E.g. “Lightroom Version is incompatible with this plugin“.

You have an old version of the plug-in.

If your plug-in has an Update button then use that to update to the latest version.

If your plug-in does not have an Update button or you are having problems using the Update feature then simply download a new version from this website and manually replace your existing plug-in.

If you have the old Picasa Web Upload plug-in then please download the Photo Upload plug-in which now replaces it. Your old Picasa Web Upload license key will work with the new Photo Upload plug-in (for the Picasa Web service).

If you have the old SkyDrive Upload plug-in then please download the Photo Upload plug-in which now replaces it. Your old SkyDrive Upload license key will work with the new Photo Upload plug-in (for the OneDrive service).

If you have the old Tree Mirror Export plug-in then please download the Photo Upload plug-in which now replaces it. Use the Tree Mirror service in the new Photo Upload plug-in.

Lightroom’s Plug-in Manager’s “Remove” button is disabled

It depends where you installed the plug-in as to whether you can use the “Remove” button to remove the plug-in from Lightroom. It is greyed out if you installed to the following locations:

On Windows, either



\Program Files\Adobe\Lightroom 5.x\Modules

On Mac,

/Library/Application Support/Adobe/Lightroom/Modules

To remove the plug-in from these locations you have to manually remove the plug-in folder from the appropriate path.

To avoid this potential problem, I recommend installing the plug-in to:

On Windows,

\Documents\Lightroom plug-ins

On Mac,


Unreceived license key

If you purchase a license for the full version of the plug-in you will be sent 2 emails. One email will contain your order number and the second email will contain your license key. These emails will be sent to you immediately and automatically by the FastSpring payment service.

The license key email should be sent immediately – but on a few occasions it has taken 6 hours before it has been received.

If you think you should have received an email but have not received it then please first check your email junk or spam folders. The license keys and order receipts are sent by FastSpring – so it may help to search your junk/spam email folders for the name “FastSpring” or “”.

When a license key email has not been received there are typically two reasons:

  1. A private\corporate email domain is not processing the email correctly (sometimes the license key emails are identified as junk\spam). The most reliable email addresses tend to be from mainstream domains such or
  2. An incorrect email address being entered during the order.

If you think either of the above apply then please contact FastSpring ( with your order number.

Unreceived license key (purchased from the Adobe Add-ons website)

If the above tips for finding your license key have not helped, AND you bought the plug-in from the Adobe website (i.e. not via the plug-in or this website) then you will need to contact Adobe for further assistance.

Please note that, as the plug-in developer and not an Adobe employee, I cannot access the payment and licensing systems used by Adobe. Therefore if you have purchased your license key from the Adobe Add-ons website you will need to contact them regarding any unreceived license keys.

Here’s a thread on the Adobe forums that gives the email address to contact that another customer was given.

Lost my license key

If you’ve bought your license from this website and lost your license key then please use the email address on the Contact page to get in touch. Please provide the reference number for your original purchase or the email address that you originally used.

Lost license keys purchased from the Adobe Add-ons website

If you’ve bought the license from the Adobe Add-ons website then you will need to contact them to have your license key sent out again.

Plug-in says the license key is invalid

When copying and pasting your license key from your license email into the plug-in, take care that the key is copied as one long list of characters.

Your email system may insert line breaks or spaces into the email, so please be sure that any such line breaks, spaces or other formatting from the email message are not pasted into the plug-in’s license text box.

If your license key is still reported as being invalid after copying and pasting it then please check you have specified the License service correctly in the license key entry window. e.g. If you have purchased a license for Dropbox then please make sure Dropbox is the selected License service in the window.

Support - License Key

A common mistake is trying to enter a Google Drive license key for Google Photos. Please be careful when purchasing licenses and entering the license keys that you have selected Google Drive or Google Photos correctly.

Can I rename the plug-in folder?

The plug-in folder should be named with a “lrplugin” or “lrdevplugin” extension. For example:




On Mac, if you open (i.e. extract) the downloaded Zip file a second time you will get a folder with the suffix “2”. Lightroom will not be able to read the plug-in from such a named folder. Before opening the Zip file consider removing an existing plug-in folder.

The following will give an error as the folder extension “.lrplugin 2” is not “.lrplugin” as Lightroom expects:

photoupload.lrplugin 2

If you really need two versions of the plug-in on your computer, I recommend having two separate parent folders and keeping the plug-in folder name the same, i.e.:


\Documents\Lightroom plug-ins\picasawebupload.lrplugin \Documents\Lightroom plug-ins\V2\picasawebupload.lrplugin


/Documents/Lightroom plug-ins/picasawebupload.lrplugin /Documents/Lightroom plug-ins/V2/picasawebupload.lrplugin

Google’s Picasa Web photo size constraints

The Picasa Web plug-in uses Google’s Picasa Web interface to upload photos to Picasa Web and Google Photos.

The Picasa Web interface has a restriction of a maximum photo size of 2048 x 2048 pixels if photos are not to be counted towards your allowance.

Please note that Google currently only provides “unlimited high quality photos” via its own mobile apps and website. Google does not allow any third party applications such as the Photo Upload plug-in to use those constraints.

However, once your photos have been uploaded to Picasa Web or Google Photos, you can then follow these instructions to recover the storage space:

Google Photos - Recover Storage

Create multiple publish services

If you want to use the Photo Upload plug-in with multiple services (e.g. Picasa Web and Google Drive) then you create additional publish services by right clicking on an additional publish service and choosing “Create new publish service…”. You can then choose a new upload service, account and settings for this additional publish service.

Checking the version of your plug-in

You may need to check which version of a plug-in you are using. You can do this from Lightroom’s Plug-in Manager.

Select the plug-in on the left (e.g. Photo Upload).

The plug-in version number is displayed on the right in both the plug-ins Settings and Status panes (in the example below the version is 1.5.5).

Support - Plug-in Manager

Removing a plug-in

Sometimes you may need to remove your plug-in, perhaps to replace it with a newer version.

Lightroom’s Plug-in Manager allows you to unregister a plug-in from Lightroom using the “Remove” button, but in most cases I recommend actually deleting the plug-in folder from your system. This is particularly important if you are upgrading the plug-in with a new version – always delete the old plug-in folder first so that there is no doubt which version of the plug-in Lightroom will be using.

You can find the installation folder of your plug-in from Lightroom’s Plug-in Manager.

Support - Plug-in Manager - Install folder

To remove the plug-in simply identify the install folder (highlighted in the above Plug-in Manager screenshot). You can then delete it using either Windows Explorer or Mac’s Finder.

You can use Lightroom’s Plug-in Manager’s “Show in Explorer” or “Show in Finder” buttons to go straight to the folder, making it easy to find the plug-in folder on your system.

Saving your log file

In order to try and help identify a problem, I may ask you to send me a plug-in log file from your machine. If I request this, please follow the instructions below:

1. Do the activity that doesn’t appear to be working, e.g. try uploading a photo. This is important so that the problematic behaviour is recorded in the log file.

2. Save your plug-in’s log file. From the “Plug-in Manager” window in Lightroom, select the “Save log” option from the plug-in’s settings section of the window.

3. Email the log file to me. Attach the log file from the place where you saved it into an email and send it to me.


1,539 responses to “Support”

  1. Jon Wright Avatar
    Jon Wright

    when I try to authenticate with twitter it says its unable to??I’ve bought the licence for it and thats working but can’t get Twitter to authenticate? On mac El Capitan with LR cc
    any help greatly appreciated

    1. Jon Wright Avatar
      Jon Wright

      sorry this is whats coming up, Connection to Twitter not available, check internet/firewall settings

      Error communicating with Twitter: ‘HTTP status 0, Unexpected network connection status – connection did not return anything.
      Check for an internet or firewall problem.’

    2. Jon Wright Avatar
      Jon Wright

      think its Little snitch thats blocking it, how do I let it accept it? tried adding process in Little snitch but can’t fine photo upload in my system? appreciate any help, thanks Jon

      1. Rob J Avatar

        By allowing Lightroom to use Little Snitch, you should also be permitting the plug-in. I’m afraid I don’t use Little Snitch, so not sure how to suggest you configure it.

        1. Rob J Avatar

          I’ve just tried Little Snitch – it sets up rules for “Adobe Lightroom” and the plug-in specifically wants permission for “Adobe Lightroom via curl”.

  2. Pieter Pretorius Avatar
    Pieter Pretorius

    I just recently discovered your plugins and they work amazingly well.

    Any thoughts about plugins for Tumblr and Viewbug?

  3. Guido Albrecht Avatar

    I`ve purchased the Flickr-Plugin. Is it possible to sync previously uploaded Albums/Photos with LR? My Photos were uploaded with the Upload-Plugin which is implemented in LR.

    1. Rob J Avatar

      I’m afraid that once you’ve set up a publish service that Lightroom does not let you move it to a different plug-in.
      Hopefully you haven’t created too many albums using the Lightroom Flickr plug-in – if not then you can manually recreate them in the Photo Upload Flickr plug-in and drag/copy over the photos.

      1. Guido Albrecht Avatar

        Hi Rob,

        Many thanks for your request. Sadly I have created a lot of Albums at Flickr. But Shit happens ;-). A little bit of mor work for me.

        BTW excuse my bad english 🙂

  4. Bob Davis Avatar
    Bob Davis

    I do not understand how resizing works. Your tutorial does not explain it. I have photos that are varying ratios due to cropping. Will resizing honor the longest or shortest dimension? Will it crop to fit? I would like to upload my photos for all to be the same height and the width varies to honor the original photo ratio. Is that possible? Resizing option to use longest or shortest dimension does not make sense.

    1. Rob J Avatar

      Hi Bob,
      Lightroom does the resizing – not the plug-in – the tutorial on this site does not explain those concepts that Lightroom looks after.
      This article I found on Google seems to be fairly comprehensive and should answer your questions:
      If you know the max height then you should be able to use Lightroom’s “Dimensions” setting to achieve what you want.

  5. Bob Davis Avatar
    Bob Davis

    I just updated to version 3.3.3. of photo upload, which I have licensed for onedrive, picasa, flickr, dropbox, and facebook. I am running lightroom cc2015.3 on a macbook pro running El Capitan OSX.

    When I upload a group of 17 photos to onedrive, 3 of the photos are generated with no preview on onedrive. I have re-tried. This is repeatable.

    1. Rob J Avatar

      The plug-in does not directly generate the file to be uploaded, nor does it generate the previews.
      Lightroom uses your export\publish settings to create the file that the plug-in uploads.
      Once the file is uploaded, the end service normally generates the preview pictures.
      You don’t mention what your export settings are – are you uploading jpegs or originals (or something else)? I’d try playing around with the different export settings that Lightroom provides and try and work out which ones generate previews in OneDrive.

      1. Bob Davis Avatar
        Bob Davis

        If Onedrive generates the previews, then this must be a problem with onedrive. I was uploading images to a new folder \jingle bell run 12-11-2015.

        I deleted it and changed to create a new folder \test.

        The images uploaded without any issues with previews.

        My settings were
        format: jpeg
        quality: 100
        color space: sRGB
        no resizing
        remove personal data from metadata

        1.  Avatar

          Hopefully it was a blip with OneDrive then?
          I said it could be Lightroom at fault as Lightroom creates the files that OneDrive makes previews from. You said the lack of previews was reproducible so there was a chance that Lightroom was not creating the upload files correctly (although in this respect Lightroom is pretty solid).

  6. Felipe Avatar

    Hi Rob and other visitors

    I’ve been using Photo Upload to sync all my photos to Flickr (~20 thousand pics) and after weeks uploading them, I realized that the ‘Taken Date’ isn’t passing through, and on Flickr, all photos are being organized by Upload Date as Taken Date fields are empty.

    Is there a way for me to update only the EXIF information through the plugin, without having to upload the whole thing all over again (again, I’m taking about 20k files!).

    Thank you!

    1. Rob J Avatar

      The plug-in does not send the EXIF information separately to the actual photo. The EXIF information is within the photo file that Lightroom generates according to your export\publish settings – and the plug-in uploads this entire file. Therefore there is no quick way to just update the EXIF information for your already uploaded photos.
      I think you need to re-upload your photos with the correct metadata setting in your export\publish settings.
      Sorry there is not a better answer for you!

  7. TomMot Avatar

    After updating to the 3.3 I lost the possibility to export photos with whole directory structure. The drop down box shows only ‘Combine (flatten)’ and ‘Last’… Any ide what has happened?

    1. Rob J Avatar

      You found a bug in the latest version which affected Tree Mirror. Apologies!
      Should now be fixed in 3.3.1.

  8. Timur Avatar

    I’ve just updated Lightroom and your plugin. Now, on “Export…” it says me:

    Photo Upload 3.2.7: Plug-in is not compatible with your version of Lightroom.

    Please update your plug-in

    This plug-in is not compatible with Lightroom 6.3

    Please update and so on…

    I obviously see that something is wrong here, but what?

    This is in fact Lightroom CC 2015.3 Release. Not sure why it claimed to be 6.3.

    1. Rob J Avatar

      There’s now an updated version (3.2.8) of the Photo Upload plug-in that allows unlicensed use with the latest Lightroom 6.3 (CC 2015.3).
      Thanks for highlighting this one.

  9. Thomas Renken Avatar
    Thomas Renken

    I am using light room CC 2015.2.1 now and the upload plug-in (version 3.2.4) won’t let Lightroom quit. It hangs up and always I have to do a force quit.

    1. James Lawson Avatar

      Basically it’s a Light room issue nothing to do with you. I had to revert to a previous Version

      1. Thomas Renken Avatar
        Thomas Renken

        I fixed this issues with the following weird work around:

        – Reset the preferences (holding down SHIFT and ALT and starting Lightroom) and choose YES.
        – Tried Quit from the menu – same problem.
        – Force exited and started Lightroom again and tried quitting by closing the window.

        After this: ALL WORKS FINE! No problems with a hanging shut down dialog. It is definitely a LR issue with the current version on MAC.

  10. Serge Avatar

    I am running plugin to do Tree Mirror export for big number of files, more than 10K files in few folders. And I have noticed some jpgs has been renamed in destination folder by adding “-2” suffix, like “DSC_1234.NEF” converted not to “DSC_1234.jpg”, how I would expect, but to “DSC_1234-2.jpg”. Original NEF-files are all OK, but destination are sometimes with, sometimes without that suffix.
    The other observation – when I run whole batch, 10K+ files few times – the same files are renamed, so this is not a random thing. And when I run only one folder out of these files – it never happened.

    What does it means?

    1. Serge Avatar

      Ok, I believe I’ve find out…
      When filename (disregarding the folder name, only the filename itself) is repeated, the plugin added suffix “-2” for destination files.
      Seems like there is a buffer for filenames (not honoring the full path) and when filename is existing the program is adding suffix to make it uniq.

      For me it seems like a bug. Is it?

      1. Rob J Avatar

        This is not a bug in the plug-in.
        The plug-in uses Lightroom’s file naming that you specify in the Export/Publish dialog. The way Lightroom exports/publishes photos means that by default it renders them all in a single (temp) folder (ignoring the source folder hierarchy) on your machine. This takes up a lot of disk space during export/publish and means that two file names cannot be the same.
        Assuming you can live without post process actions then the plug-in setting “Generate exports one at a time” will work around the Lightroom problem:
        Let me know how you get on.

  11. James Lawson Avatar

    I am using light room 6 now and the upload plug-in won’t let Lightroom quit it hangs up and I have to do a force quit

    1. Rob J Avatar

      I’ve sent you an email asking for more information about this one. Please get in touch.
      I’ve not seen the problem myself, so I think I need to understand more about what has changed on your system. Please make sure you are running the latest version of the plug-in.

    2. Bob Davis Avatar
      Bob Davis

      I don’t know if this applies but wanted to mention that a very unstable (crashes and hangs) release of Lightroom for Mac came out about a week ago. Adobe issued a stability update about two days after that.

    3. Rob J Avatar

      The problem was resolved when the plug-in was updated to the latest version.

  12. calvin Avatar

    Just upgraded the free version to 3.1.8 for PS CC and find I can’t set my upload option to FLICKR with a Privacy setting of Public. It is set at PRIVATE with no option to change. Looking at the help it doesn’t suggest this is not available o the free version, but can someone confirm or advise of solution.


    1. Rob J Avatar

      The setting to have all Flickr photos uploaded as Public rather than Private is restricted only to the licensed/paid-for version of the plug-in.
      You can use the Flickr web site to change the privacy status of your photos, but this could be a pain if you have a lot of photos.

  13. Dana gonzales Avatar

    I purchased the license for the Amazon Cloud Drive and it all works but I have two problems.
    1. When loading DNG files it makes a very small 256 x 205
    file for viewing.. way to small for me. It does load the DNG perfectly.

    2. When loading Tiff files the file that shows up on amazon is all white white with just a little bit of the photo coming through and once again it did load the full size Tiff but the display image is incorrect.

    Otherwise it seems like a very good product once these issues are worked out

    1. Rob J Avatar

      The behaviour you’re seeing for DNGs and TIFFs is really down to how you’ve set your photos to be exported from Lightroom, and how Amazon Cloud Drive handles viewing them.
      If you exported the photos from Lightroom to your hard drive (i.e. without using the Photo Upload plug-in) and then used the web interface for Amazon Cloud Drive to upload them, you would see the same behaviour.
      I tried exporting and uploading DNG files myself and agree that there is a small image displayed in Amazon. There are some export settings provided by Lightroom for DNGs, such as the size for “JPEG Preview”. But in my experience changing these did not appear to make much difference to the size of the preview picture in Amazon.
      I also tried exporting and uploading TIFF files, and these worked out ok for me – correct photo and full size.
      I’d suggest playing with the setting in Lightroom – under “File Settings”. I’m pretty sure the plug-in is not behaving any differently than if you exported the files to disk and then uploaded them manually to Amazon Cloud Drive.

  14. Andreas König Avatar
    Andreas König

    Just installed Photo Upload, and setting up the connection to Amazon Cloud Drive seemed to have worked fine (authentification worked, it shows how much space I have left, I could rename the collection and it created a folder with that name in the amazon cloud drive). But when I try to publish the collection (with one picture), I get the error message:

    Error communicating with Amazon Cloud Drive: ‘HTTP status 0, Unexpected network connection status – connection did not return anything.
    Check for an internet or firewall problem.’ (1)

    But as said, internet connection is ok, and there is no firewall.

    1. Rob J Avatar

      Yes! You found a bug that was accidentally introduced in the last version (2 days ago).
      This is now fixed in the latest version (3.1.6).
      You can use the Update button to update to the latest version.
      Apologies, and many thanks for raising the issue.

  15. John Hunter Avatar
    John Hunter

    Having problems with Flickr uploads today from Lightroom 4.
    I upgraded to latest plugin version and re-authorized plugin. Any thoughts? Also getting an error creating a new folder.

    Getting this error: (I removed some of the token data)
    Error communicating with Flickr: ‘HTTP status 401, oauth_problem=signature_invalid&debug_sbs=POST&********%26oauth_nonce*******%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1442513196%26oauth_token*******%26oauth_version%3D1.0%26title%3DFall%2520Wreath-18-2.jpg’ (1)
    D:\Pictures\Lightroom\2015\September 14\Fall Wreath-18-2.dng

    1. Rob J Avatar

      Flickr seems to have had a few problems today.
      It was very intermittent for me earlier when I was testing the plug-in, but now seems to be working. Perhaps give it another go?

      1. John H Avatar
        John H

        Thanks Rob. It’s been working fine since that day. As you say, probably a Flickr issue that day.
        Thanks agan.

  16. Jesse Avatar


    This morning I started receiving this error:

    Error communicating with Flickr: ‘HTTP status 401, oauth_problem=signature_invalid&debug_sbs=POST&’ (1)

    I updated the plugin, restarted lightroom, and am still having the error. Please help.


    1. Rob J Avatar

      Yes – apparently so(!) Thanks for raising the problem.
      Something has changed on the Flickr side recently that appears to have had a bad effect when trying to upload photos using this plug-in.
      This should now be fixed in version 3.1.4 of the Photo Upload plug-in.
      Can you update to this version and let me know how you get on?

      1. Jesse Avatar


        Flickr seems to be working again today. Thank you for all of your help!


        1. Rob J Avatar

          Thanks for confirming – Flickr seems to be working just fine for me too today.

  17. Albert Dandl Avatar


    Can I use the license (for Dropbox) on two computers?
    I have Lightroom CC and have it installed on two as well.

    Thank you!


    1. Rob J Avatar

      Hi, the policy is to have as many licenses for the plugin as you require for Lightroom. So if you are following Adobe’s policy for using a single Lightroom license on one desktop and one laptop then you can use one license of the plugin for the same.

  18. Jan Rifkinson Avatar
    Jan Rifkinson

    When I try to upload to Zenfolio, I get the following error:
    Zenfolio does not permit uploading directly to the Group named…. whatever

    Zenfolio tech support does not recognize this error, so I’m turning to you. Help pls. Thanks

    1. Rob J Avatar

      This sounds like you are trying to upload photos to a Zenfolio group. Zenfolio groups are collections of Zenfolio galleries and cannot themselves contain photos. Please choose a Zenfolio gallery rather than a Zenfolio group during however you are doing your upload.

      1. Geoff Cusick Avatar
        Geoff Cusick

        A follow on to this – I’m evaluating options for uploading to Zenfolio.

        Is it possible to select a Gallery within a specified Group for export (or Publish)? (…in the licensed version, I realise).


        1. Rob J Avatar

          Yes, absolutely. Even in the free version you should be able to see the list of available groups and galleries in the album selection drop down (but your selection will be ignored in the free version).

      2. Geoff Cusick Avatar

        Hi Rob,
        I’m currently evaluating options for managing a Zenfolio site; your plugins look as if they will do the job, but can I confirm that it is possible to select a specified Gallery, within a specified Group?.


        1. Geoff Cusick Avatar

          Sorry. Fat Finger Syndrome. Thanks for the rapid response.


  19. David Gómez-Rosado Avatar

    I just purchased Upload to Flickr… but I get th following error:

    An internal error has occurred: Service_FL.lua:127: attempt to index global ‘NPPPlugin’ (a nil value)



    1. Rob J Avatar

      You found a bug – sorry!
      Should now be fixed in version 3.1 – please use the Update button within the plug-in in Lightroom’s Plug-in Manager to update to 3.1.

  20. James Avatar

    What makes your SmugMug plugin better than the free one provided by SmugMug themselves? I couldn’t find the difference from your features list.

    1. Rob J Avatar

      Hi, the Photo Upload plugin allows you to Export from Lightroom to SmugMug as well as use Publish Services. Other than that, the interface is a little different between the plugins, so it’s really down to personal preference. You can use Photo Upload to upload to many different services, so some people prefer using the same user interface for all their connected services.

  21. Mario Avatar

    I am using the plugin to publish to Google Photos. Even though I have set the plugin to reduce the size of the photos to under 16MP the photos still always seem to count towards my Google storage and fills up my Google storage allowance. Any ideas?

    1. Rob J Avatar

      Hmmm – after some investigation, it appears that Picasa Web is (still) limited to photos of 2048 x 2048 (or less) not counting towards your limit. It appears you have to use the Google apps (on your phone or via their website) to upload photos up to 16MP that do not count towards your limit.
      Sorry, there is nothing more the plug-in can do until Google relax their older limits.

  22. Andrew Koenig Avatar
    Andrew Koenig

    When use Photo Upload to create a Facebook album, each photo winds up with the file name as its caption. Is there a way to turn off these captions?

    1. Rob J Avatar

      Hi, you can use the Settings windows to specify a value for “Photo title” which is used as the photo name in Facebook. You can choose a few different options – try selecting something other than “File name”.
      Thanks, Rob.

      1. Andrew Koenig Avatar
        Andrew Koenig

        I see no setting for “Photo Title;” just for file name.

        1. Rob J Avatar

          The “Settings” button is available in the Export or Publishing Manager dialog in the “Photo Upload – Account” section. Which is the section above “File Naming”.
          Can you see the Settings button? When you click it and open the settings window you can choose what makes up the “Photo title”.

          1. Andrew Koenig Avatar
            Andrew Koenig

            Found it; thanks! I’ll try that next time I create a Facebook album and see what happens.

  23. ken k Avatar
    ken k

    I am interested in using several of the publish service (7 different ones). Is there a discount when ordering multiple services?

    1. Rob J Avatar

      I’m afraid there is not a discount system in place. Sorry!

  24. Rick Carmichael Avatar

    Hi Rob,

    Thanks for the VERY fast response.

    I incorrectly referred to Facebook as you indicated. This problem is only something I noticed with Flickr and I was always looking through my close to 3000 photos on that site to see if there were any remnant thumb images still there. I WAS in fact using an out-dated version and am now downloading 3.0.7.

    I did find the right location for the plugin and replaced my logo with the temporary thumb that you provide. I’ll probably do that again with the new version of the plugin. (Even though I now understand that it’s going to be deleted when the upload completes.

    Thanks again for your hard work on the plugin and also for your TRULY WONDERFUL SUPPORT!

    Rick Carmichael

    Founder – LuxViz

    Creative Media for Promoting Luxury Properties & Lifestyles

    Jl Raya Canggu 155
    Canggu, Bali, Indonesia 80361

    +62 (0)878 610 33533

  25. Cathy Avatar

    I have just purchased photo upload for one drive as a plug in to lightroom. It was all going well I uploaded photos to a named file – next time I looked they all disappeared out of the file. I tried again – “non sharing” but same happened. It may be when I upload a further batch to a different file – so far the last batch have stayed but I wouldn’t be surprised if they also disappeared – really annoying – spent ages uploading – what am I doing wrong? They were there then I saw the counter going down. I pay for one drive 1TB in monthly subscription with Microsoft office etc. I have LR creative cloud 1 on windows & 1 on apple mac. I am using windows 7 laptop to upload. Thank you for any suggestions.

    1. Rob J Avatar

      I think I need some more info about this. Are you using different OneDrive accounts and shared folders? That may explain why sometimes photos appear not to be visible. I don’t think the plugin is doing anything strange. Please contact me at if you think I can help further.

  26. Pierre Avatar

    Thank you for your answers, it does work but is there a way to see the status of the uploading? I got some error reports from LR saying 4 pics haven’t been upoaded, but I don’t know if it’s still uploading or not, an all the files in the folder haven’t been uploaded yet. If I do a new upload of the same folder, will that create doubles or will it only upload pics that haven’t been uploaded yet?
    Many thanks!

    1. Rob J Avatar

      If you see the message saying some photos have not uploaded then that means the Upload has finished. You should have an indication of why some photos did not upload in the message.

  27. Jonathan Avatar

    “Error Uploading to Zenfolio”

    I have uploaded some photos to Zenfolio from Lightroom 6.1.1 using your licensed plug-in. Some of the photos’ metadata and/or developing has changed, and they are listed in LR as “Modified photos to republish”. When I click “publish”, I get the error “Error Uploading to Zenfolio – HTTP Status 200. An unexpected error has occurred. Please try again later. Code = nil”. I can provide a screenshot and my log file if you like. I tried quitting LR and restarting but no change.
    I’m using the latest version, just installed (3.0.4)

    Appreciate some assistance with this please. Thanks!

    Apart from this glitch, I love your plug-in!! 🙂

    1. Rob J Avatar

      Sorry you’re having problems.
      I sent you an email asking for you to send me your log file.

      1. Jonathan Avatar

        Hi Rob,

        The new version works fine.

        Terrific customer service and responsiveness.

        Thank you so much! 🙂

  28. Europoint Avatar

    I’m thinking about buying a license PHOTO UPLOAD FOR ONEDRIVE, but I have one question.
    It is possible to use the Lightroom plugin PHOTO UPLOAD for two different accounts Onedrive (one working, second private – other email addresses) at the same time?
    I can’t seem to add a second account. Is it possible?
    Thank you

    1. Rob J Avatar

      Yes – you can use the plug-in with multiple OneDrive accounts.
      The plug-in uses the account you are currently logged into in your default Web browser.
      Either log out of that OneDrive account in your browser, or log in with your second account in the browser prior to running the plug-in authentication via the plug-in’s Add/Refresh button.

  29. Jack MacDonald Avatar
    Jack MacDonald

    Have used full version of TreeMirror for several months. Updated today to 3.0.4. Having a problem with file location; hopefully it is something you can address, but I will understand if it’s deemed too “exotic”.

    I import photos to D:\Photos\yyyy\mm using a Lightroom preset. When I am (mostly) done with editing the photos, I move them to my network server (Z:\Photos\yyyy\mm) using Lightroom. The folder structure is identical, just located on a different drive. I do all the heavy lifting when the photos are on the local disk because the network connection is via WiFi, and is relatively slow.

    The Settings for TreeMirror reference the Z-drive location, and it works fine when the photos are located on Z-drive. However, if I try to publish the photos before moving them to Z-drive, then TreeMirror issues an error message because it cannot find the photos on Z-drive; they still reside on D-drive.

    I get confused each time this event happens; I must recall why the publication failed, and that it’s not really a problem.

    The workaround is easy – just move the photos to their final location before publishing, but I was hoping there might be a more elegant solution that would allow them to be published before they are moved. Maybe there could be two sources in the Settings (e.g., Z:\Photos; D:\Photos).

    It’s TreeMirror that requires the exact matching between the Settings and the photo location. Lightroom itself is happy with the photos in either location.

    1. Rob J Avatar

      Your request does indeed make sense. And as you point out it probably falls into the “exotic” category.
      The challenge for the plug-in is to allow you to have multiple “source bath folder” paths, but not to complicate the settings window (further) for the majority of other people.
      Hmmm. I’ll think about this one.
      Thanks for your feedback.

      1. Jack MacDonald Avatar
        Jack MacDonald

        I agree – KISS for the interface. A semi-colon delimited list of source folders could work. Most users would simply enter a single value, while others could provide additional sources in the same field.
        PS – presently moving files onto the server… but don’t let that deter you from enhancing your plug-in 😉

  30. Pierre Avatar

    Is it possible to export to onedrive using photo upload all the files imported by Lightroom, including raw files ? Is it possible to export it in the same folders structure as it is on my mac?

    1. Rob J Avatar

      Yes is the answer – you’ll want to follow these instructions to export your photos with their folder hierarchy:
      You will also probably want to turn on the setting to generate photos one at a time if you’re doing a large batch:
      My recommendation is to try exporting the photos in smaller chunks – just to make it manageable and check things are going well.

  31. Jahred Avatar

    Hi, I’m testing out this out on a laptop with a sub-1080p resolution and have found that the settings menu trails off of the bottom of the screen. The only way to change the bottom few options as well as hit ok and confirm it seems is to change the screen orientation by way of “ctrl+alt+[arrow key].” Definitely a great product however, and I plan on purchasing a license soon despite this small annoyance from my budget machine. Just thought I’d report the issue.

    1. Rob J Avatar

      Ah – I spotted this myself the other day and knew I’d have to do something about it. You beat me 🙂
      Thanks for highlighting it – I’ll try and work out how to make the Settings window wider and less deep.

      1. Jahred Avatar

        Thanks! I’m already loving the convenience of this plugin. Also just wondering, is there a way to transfer my license from one device to another? Just thinking ahead is all.

        1. Rob J Avatar

          Yes – you can transfer the license. You need a license for the plug-in for each license of Lightroom that you use it with.

  32. David Kearley Avatar
    David Kearley

    Hi there, just bought the zenfolio plug in. This may be a silly question. When I upload a picture or album to my zenfolio page is there anyway I can keep it on the site even though I have deleted the collection under the publish window? I’ve tried and it seems to delete the files off the site aswel

    1. Rob J Avatar

      If you create an album with a photo on Zenfolio from Lightroom, you should be able to right click on the album in Lightroom, choose Delete and a Confirm window will appear. This will give you an option to “Leave on Service” – which will delete the album and photo from Lightroom but leave them on Zenfolio.
      That sounds like it should suit your needs?

      1. David Kearley Avatar
        David Kearley

        Thank you for the quick response. Yep that’s just what I needed. One more question if possible, last night when I was testing I had no problems uploading to my zenfolio folders but now I get a window saying zenfolio does not permit uploading directly to the group (name of group). Is this a problem on the zenfolio end?

        1. Rob J Avatar

          It sounds like you’re trying to upload photos to a Zenfolio group, rather than a Zenfolio gallery. Please make sure the album you’re selecting is a gallery not a group.
          Does that help?

          1. David Kearley Avatar
            David Kearley

            It was adding an album to an already set up group seems to put up the error via re-directing. Choosing album on zenfolio seems to do the trick. Thanks again for everything

          2. Rob J Avatar

            Yeah – that sounds correct. When using the “redirect” option, it matters whether the album you are redirecting to is a Zenfolio group or a gallery. Thanks.

  33. Robert Avatar

    I have recently changed the account name (email address) for my OneDrive. Unfortunately, my old account name comes alphabetically before my new account name, with the result that every time I load the plugin I get an authentication error and I have to select the correct name.
    Is there any way that I can delete the old account name from the plugin?

    1. Rob J Avatar

      Can you select the old account name in the list and then click the “Remove” button below the list of accounts?
      Can you also confirm that you have the latest version (3.0.3) of the plug-in?

    2. Robert Avatar

      It’s OK, I have solved this now. I haven’t a clue how I did it, though 🙂

  34. Scott Vinnicombe Avatar
    Scott Vinnicombe

    HI Rob,
    I am getting a http error when trying to upload a file. ( no response from WordPress Site)
    So I disconnected the plugin from the site and when I tried to reconnect I got a similar error message.. there was no response from my wordpress site. (This was after I entered the code and the plugin was trying to retreive my account details.)

    Silly thing is when I first tried to upload an image .. it uploaded then I got the error.

    Further update..
    After trying a few more times .. ti works as you suggest, replacing existing photos.
    I am not sure why I got the initial errors, but see how we go.
    Thanks very much for this, it gives me similar functionality to my Joomla site. Now I am happy to keep going with WP.


    1. Rob J Avatar

      I’m going to put those WordPress errors down to a temporary problem on the servers.
      Let me know if they repeatedly occur again.
      Glad the plug-in is now more useful for you!

      1. Scott Vinnicombe Avatar
        Scott Vinnicombe

        Hi Rob,
        Still occasionally getting http errors(error 400).. no response from WordPress (or jetpack) it varies.
        I think it is my site so I am not too worried at the moment.
        Something I discovered today .. I rename my files as part of my workflow and today I added © in the file name.
        After I have uploaded to WP.. the image just gets a number (and the thumbnails the same) as the file name and jpg is missing from the file extension. So the file would just simply be called 1 (or 2 or …)
        Strangely enough you can still see the image in the media folder, but when you try to use it in a slider/post or page the image does not appear.

        Took me a while to troubleshoot that, but as soon as I removed the © all the file naming came back as normal. Just thought you might like to know.
        I am still happy with the plug in as it is doing basically what it’s meant to.


  35. Stephen Bokat Avatar
    Stephen Bokat

    I have Lightroom 4, running the paid version of Photo Upload. If I update to Lightroom 6, do I need to reinstall Photo Upload? Will my existing license cover the new version of Lightroom?

    1. Rob J Avatar

      If you reinstall Lightroom over the top of your old version 4 then you should not need to reinstall the plugin.
      Your existing license will work with Lightroom 6, but make sure you are running the latest version of the plugin.

  36. Scott Vinnicombe Avatar

    HI Rob,
    I am using photo upload to publish from lightroom to WordPress.
    If I republish a photo, i get duplicate photos in my WordPress media manager.
    The original file is not updated.

    Any ideas?


    1. Rob J Avatar

      WordPress does not allow plugins to update photos in the same way that other services permit.
      I don’t think there is a solution to this without WordPress updating the APIs they provide.
      I’ll keep an eye on any enhancements that WordPress provide.

      1. Rob J Avatar

        Actually… I’ll do some further investigations into this. I did notice some new features so perhaps the plug-in can adopt those. I’ll get back to you…

        1. Scott Vinnicombe Avatar
          Scott Vinnicombe

          Great, Thanks!

    2. Rob J Avatar

      The latest version of the plug-in (3.0.3) is now updated so that photos can be deleted and duplicated on WordPress. I think this will now work for you – WordPress posts and pages refer to the file name of the photo, so assuming the updated photo has the same file name then the plug-in will effectively be “updating” the photo on WordPress (by deleting and then re-uploading with the same file name).
      Let me know how you get on.

  37. Simon Clausen Avatar
    Simon Clausen

    have rights over my photos when I give them acces via LR? im confused about this service?

    1. Rob J Avatar

      No – the Photo Upload plug-in does not have any rights over your photos.
      I think you are trying to authenticate with OneDrive (correct?), in which case the message is saying that the plug-in is requesting authentication with your OneDrive account (so that it can upload your photos). Most online providers, such as OneDrive, have such a mechanism in place to make sure that only apps and plug-ins that you authorise can connect to your account.
      There is some information on the plug-in’s authentication here:
      Does that help?

  38. Vince Avatar

    Hi, I’m using Plugin v. 3.0 and Lightroom CC. I get errors when opening the application and also when closing. Both read:

    Couldn’t read file “/Users/vincsam/Library/Application Support/Adobe/Lightroom/Photo Upload.log” into memory.

    When closing Lightroom, there is also an additional error saying that a shutdown task for Photo Uploader became unresponsive and may not have been completed. This has been going on for some time now. Any thoughts?

    1. Rob J Avatar

      We’ve solved this issue offline.
      The problem seemed to be either incorrect file permissions for the log file or a corrupt file. Either way, renaming (or deleting) the log file referenced in the error message causes the plug-in to write to a new file – and this appears to have solved the issue.
      If anyone else reading this experiences the problem, kindly let me know and perhaps the plug-in can include a fix, but at this time I’m putting it down to a complete “one-off”.

      1. David Howard Avatar
        David Howard

        I had the same issue with the “Plug-In ‘Photo Upload’ performing shutdown tasks” hanging when quitting lightroom CC. I deleted the log file and it fixed it. I am on Photo Upload version 3.2.4, and Lightroom version 2015.2.1.


  39. Jesse K Avatar
    Jesse K

    Hi, I noticed that when I upload files to flickr the Photo Upload plugin also uploads its own logo. Is there a way to stop this?

    Also, is there a way to upload directly into my photostream but not into an album?

    Thank you,

    1. Rob J Avatar

      The plug-in does create a temp logo in the Flickr folder and then deletes it when it has finished uploading all the photos. If it is not deleting this then you’ve found a bug. Are you using the latest plug-in version 3.0?
      Re. uploading to your photostream, you don’t mention if you are exporting or publishing your photos.
      If exporting then you can choose the album “[Photostream]” in the album selection box.
      If publishing then when you edit the album in your publish service you can choose “Redirect to album on Flickr” and choose “[Photostream]” in the selection box.

      1. Jesse K Avatar
        Jesse K


        I did not realize it was a temporary logo. It appears to have been deleted, thank you for letting me know that this is normal.

        Also, I am using the “publish” method of uploading, thank you for showing me how to accomplish what I needed.

        The plugin is great so thank you for it, and thank you for responding so quickly to my questions!


  40. helen Avatar

    …. and it works! Thank you!

  41. Robert P Avatar

    I have just upgraded LR to 6.1, and I have also updated Photo Upload to 2.9.9. The plug in no longer works – I get the message that it is not compatible with LR6.1

    1. Rob J Avatar

      I’ll be releasing a new version of the plugin later today that is compatible with 6.1. Thanks, Rob.

      1. Rob J Avatar

        There’s now a version 3.0 of the plug-in which is compatible with today’s release of Lightroom CC 2015/6.1.
        Please update your plug-in…

        1. Robert P Avatar

          Thanks, Rob. That worked fine.

  42. helen Avatar

    I just updated to Lightroom CC 2015 and I get a message that says that the plugin is not compatible. Will you be providing an update?

    1. Rob J Avatar

      Yes – the latest version of the plug-in is compatible with Lightroom 6\CC. You can either upgrade using the Update button in the plug-in settings or you can download the latest version from this website and manually upgrade.

      1. helen Avatar

        I tried the update button and, while it seemed to go through the process and reported success, the plugin doesn’t work and still requests an upgrade.

          1. JPL Avatar

            the same happens to me

          2. Rob J Avatar

            Ah! I’ve missed the release of version 6.1. I’ll make a new version available later today and be back in touch at that time. Thanks, Rob.

          3. helen Avatar

            Great. Thanks, Rob.

          4. Rob J Avatar

            Ok – sorry for the delay, but there’s now a version 3.0 of the plug-in which is compatible with today’s release of Lightroom CC 2015/6.1.
            Please update your plug-in…

  43. Anna Avatar

    I am trying to upload to Zenfolio. I have the latest version and the license fee is accepted. 2 days ago the process worked fine. Now I keep on getting this message. An internal error has occurred: Service_ZF.lua:1069: attempt to index local ‘successfulUpload’ (a nil value). Please help!

    1. Rob J Avatar

      Unfortunately you found a bug. It should now be fixed in version 2.9.9.
      Can you use the Update button to upgrade to the latest?

  44. Mark Lacy Avatar
    Mark Lacy

    Cant update from 2.8.4 to 2.9.8

    Photo Upload: could not update plug-in. [Zenfolio]
    Unable to update existing plug in (permission problem?)

    What to do?

    1. Rob J Avatar

      If the plug-in cannot update itself then you should manually download the latest version, remove/delete the old version from your system and extract and install the new version from the downloaded zip (as if you were installing for the first time).

      1. Mark Lacy Avatar
        Mark Lacy

        I must have deleted something in the wrong order trying to update. When I try to delete published service it says:

        Can’t deleted published collection. Internal error: assertion failed!

        Still stuck. User error trying upgrade.

        1. Rob J Avatar

          Hmmm. So did you delete your plug-in (delete the whole folder from your computer), download the latest version, and re-install it?
          You should not need to delete your publish service in Lightroom.


          1. Mark Lacy Avatar

            This what happens when you don’t a first read directions.

            First I downloaded the update in just copied the new files over the old files in the plugin folder. didn’t work.

            Then I deleted the plugin folder entirely and and installed the new plugin folder from the download. Hasn’t worked.

            Last I tried deleting the published service inside lightroom hence the error. Now I am all confused.

  45. Laurent Avatar

    It is possible to set up to 8 keywords for each image in OneDrive (web interface). Do you think you will introduce this feature in a (near) future release?

    Thanks. Laurent

    1. Rob J Avatar

      Thanks for the suggestion – I’ll look into this and if it’s possible I’ll make sure the plug-in is updated to handle keywords for OneDrive.

  46. David Brooks Avatar

    Hi, my upload using Lightroom Export on Mac starts OK and the first few photos are visible on Google Photos. But then it seems to drop out and stop with an error message “An internal error has occurred. Export.lua:1223:table index is nil”

    Lightroom tells me in the status bar the export is still in progress but nothing happens. I am using iMac 27 2011 and Lightroom CC

    1. Rob J Avatar

      Yes – the last fix did not go to plan! It should now work correct in version 2.9.7.
      Please use the plug-in’s Update button to get the latest version.
      Thanks for raising this!

  47. Sven Wardle Avatar
    Sven Wardle

    I have successfully installed the Photo Upload Plug In using Adobe Extension Manager after purchasing it from the Adobe Plug Ins page.
    How do I now add the plugin to Lightroom? I cannot add it via the Plug In manager because the folder containing the file is a .zxp file. Apologies if this is a stupid question.

    1. Rob J Avatar

      Please follow these installation instructions:
      You can download the plug-in as a zip from the instructions on that page.
      Adobe make installation of plug-ins very difficult by making you use Adobe Extension Manager and ZXPs. The theory is that when you “install” the plug-in via Adobe Exchange Manager all it actually does is extract the zip file from the ZXP and put it in your machine’s downloads folder. My advice is to ignore Adobe’s convoluted installation process and follow the instructions from the above link.

  48. neizo Avatar

    Lightroom3.6、Photo Upload 2.9.5 to OneDrive
    After send one photo,Appear this Alart and
    “An internal error has occurred  : Export.lua:1208: table index is nil”

    1. Rob J Avatar

      Yes – you found a bug! The plug-in had lost compatibility with Lightroom 3.x.
      It is now fixed, please use the Update button to update to version 2.9.6.
      Many thanks for highlighting the problem,

  49. Henry Dechert Avatar

    I fired up LR (5.7) while on a trip and didn’t have all drives that contain my LR folders connected.

    When I opened the Smug-Mug upload folder account in Publish Services, LR then attempted to update everything, and kept sending error messages.

  50. Andy Avatar

    I am using Photo Upload for OneDrive. I had to reinstall Lightroom and need to repopulate my folder and album structure. How can this be done?

    1. Rob J Avatar

      Assuming you want to recreate the folder structure on your local computer that you have on OneDrive – then the plug-in will not do this for you.
      I suggest using the OneDrive client from Microsoft to re-sync your folders.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.