-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for High quality instead of Original full resolution #22
Comments
Hello - I may be wrong, but I also ran into this problem and when I looked into it, it would appear that the Google API that facilitates the upload only allows original full resolution uploads. I had to follow the below instructions to compress any images uploaded. I was uploading a lot of images so for me it was easier to buy 100gb of space for a month, upload everything i needed, compress the images every day and then cancel my 100gb subscription. Hope that helps How to Recover Storage on Google Photos
Depending on the size of the images and videos uploaded in Original quality, it may take time. You can close the windows and come back later to check how much storage was recovered. You can note down the amount of storage space left, which is available with the Original radio button option. Note: You can only restore storage once a day. |
Thanks for the suggestions and quick response |
@grantpinkerton thanks for the response to @liliandjeff. I'll reopen this issue to at least make it clearer in the app that the originals are always uploaded. The app already warns at the bottom that the the uploads will count towards the Google storage, but perhaps the warning could be more pronounced and worded clearer. |
Looks like the upload is original full resolution. My Google Photos account setting is High quality (free unlimited storage). Getting error INVALID_ARGUMENT: The remaining storage in the user's account is not enough to perform this operation.
Can you honor the upload setting or provide a Jiotty setting for upload resolution? Thanks
The text was updated successfully, but these errors were encountered: