# Onebox support for new Google Photos
**URL:** https://meta.discourse.org/t/onebox-support-for-new-google-photos/30106
**Category:** Feature
**Tags:** onebox
**Created:** [June 17, 2015, 12:49am UTC](https://meta.discourse.org/t/onebox-support-for-new-google-photos/30106 "2015-06-17T00:49:12Z")
**Posts on this page:** 19
**Page:** 1
### Author:  [@ky\_metro](https://meta.discourse.org/u/ky_metro)
#### Post date: [June 17, 2015, 12:49am UTC](https://meta.discourse.org/t/onebox-support-for-new-google-photos/30106/1 "2015-06-17T00:49:12Z")
Google+ Photos was a default for many of us with Android and Auto-Backup turned on… all your photos end up in one place online, free storage, etc etc… I’ve been in the habit of opening them on the Google page, and dragging the photo into Discourse. The photo URL _used to look_ something like this:
[https://lh3.googleusercontent.com/-DDzM12G2Qwc/VWlw-u8s6RI/AAAAAAABlio/PjSwWb\_IOJQ/w1556-h875-no/IMG\_20150529\_201713.jpg](https://lh3.googleusercontent.com/-DDzM12G2Qwc/VWlw-u8s6RI/AAAAAAABlio/PjSwWb_IOJQ/w1556-h875-no/IMG_20150529_201713.jpg)
This oneboxes just fine:
Now we have Google Photos (they dropped the Plus)… and they’ve changed the way photo URLs work.
Same photo, new Google Photos URL:
This will not onebox, as it’s not “.jpg” . I have no idea how to extract the raw jpg location from that string. It appears to be a completely different storage location and id, and contains photo size information at the end.
Can someone smarter than me please look into adding/fixing this?
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [June 17, 2015, 6:26pm UTC](https://meta.discourse.org/t/onebox-support-for-new-google-photos/30106/2 "2015-06-17T18:26:50Z")
Sure @techapj can you add this to your list?
---
### Author:  [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)
#### Post date: [June 17, 2015, 9:32pm UTC](https://meta.discourse.org/t/onebox-support-for-new-google-photos/30106/3 "2015-06-17T21:32:03Z")
There might be a few things to consider here in terms of where users get their URL’s from.
Here are 4 links:
- Page URL when image is viewed as myself
- [https://photos.google.com/photo/AF1QipMtn-OGRU9JOUmwnBFmPKNn3EZnbUvEc504\_1ez](https://photos.google.com/photo/AF1QipMtn-OGRU9JOUmwnBFmPKNn3EZnbUvEc504_1ez)
- prompts for authentication when viewed as any other user.
- Get “Share” link from above page
- [https://goo.gl/photos/kqi5hm6HdA5J9ksi7](https://goo.gl/photos/kqi5hm6HdA5J9ksi7)
- Displays page, image, author, date and option to download.
- It takes a few seconds for Google to generate this share URL when chosen.
- Direct image link
- [https://lh3.googleusercontent.com/eTnYUj6Fw8jZL3YMxLMlGS1CqDoxxZ1tTDvAITi2SFA=w500-h333-no](https://lh3.googleusercontent.com/eTnYUj6Fw8jZL3YMxLMlGS1CqDoxxZ1tTDvAITi2SFA=w500-h333-no)
- This is obtained by right clicking on the image and selecting “Copy image URL”
- Raw image
- Not sure I’d trust this to continue working in the future - no indications that this is a permalink. Guess it might be removed / moved in Google’s delivery network.
- Selecting 3 images and then selecting “Share”
- [https://goo.gl/photos/KKiG8XvS4o9BXy2r9](https://goo.gl/photos/KKiG8XvS4o9BXy2r9)
- Displays gallery page, multiple images, author, date and option to download.
- Again takes a few seconds for Google to generate this share URL when chosen.
---
### Author:  [@Patrick\_David](https://meta.discourse.org/u/Patrick_David)
#### Post date: [September 22, 2015, 1:55pm UTC](https://meta.discourse.org/t/onebox-support-for-new-google-photos/30106/4 "2015-09-22T13:55:06Z")
Just checking in to see if there’s been any movement on this? I recently ran into the same problem for a user.
---
### Author:  [@lrossouw](https://meta.discourse.org/u/lrossouw)
#### Post date: [July 22, 2016, 11:43am UTC](https://meta.discourse.org/t/onebox-support-for-new-google-photos/30106/5 "2016-07-22T11:43:54Z")
It would be great if we can get these `https://goo.gl/photos/KKiG8XvS4o9BXy2r9` style links oneboxed. Both the photo and gallery versions.
---
### Author:  [@cpradio](https://meta.discourse.org/u/cpradio)
#### Post date: [July 22, 2016, 12:14pm UTC](https://meta.discourse.org/t/onebox-support-for-new-google-photos/30106/6 "2016-07-22T12:14:25Z")
Thank link doesn’t seem to work for me, can you paste a working version in [Generate responsive embed codes - Iframely](https://iframely.com/embed) to see if it is even supported? (particularly for gallery versions)
---
### Author:  [@lrossouw](https://meta.discourse.org/u/lrossouw)
#### Post date: [July 22, 2016, 1:34pm UTC](https://meta.discourse.org/t/onebox-support-for-new-google-photos/30106/7 "2016-07-22T13:34:26Z")
Cool they seem to work actually. I added goo.gl to my site’s onebox settings and they work now. I don’t know why I thought I didn’t need to do that.
I also edited the link as I copied one of the ones above but with the link count number at the end by mistake.
---
### Author:  [@lrossouw](https://meta.discourse.org/u/lrossouw)
#### Post date: [July 22, 2016, 2:00pm UTC](https://meta.discourse.org/t/onebox-support-for-new-google-photos/30106/8 "2016-07-22T14:00:57Z")
Only drawback it seems is that Google shows only the top of portrait images.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [July 22, 2016, 7:30pm UTC](https://meta.discourse.org/t/onebox-support-for-new-google-photos/30106/9 "2016-07-22T19:30:01Z")
There is no way URL shorteners would be expected to work here. None whatsoever.
---
### Author:  [@lrossouw](https://meta.discourse.org/u/lrossouw)
#### Post date: [July 23, 2016, 1:29am UTC](https://meta.discourse.org/t/onebox-support-for-new-google-photos/30106/10 "2016-07-23T01:29:06Z")
It does work if you whitelist goo.gl. Also if you share a photo from Google Photos it generates a special goo.gl link (similar to the maps specific one) that’s just for photos. So it’s not a standard shortened link. On my site I white-listed goo.gl and if you post this link it puts the photo in.
Only problem is that portrait mode photos are cut-off. But I think that’s something wrong on Google’s end.
See this:
> **[Iframely URL Debugger - Open Graph, Twitter Cards, oEmbed](https://debug.iframely.com?uri=https%3A%2F%2Fgoo.gl%2Fphotos%2FgviT7KkEkKv2BKdJ7)**
>
> Check your URL against Open Graph, Twitter Cards, oEmbed specs. See what other apps see.
That photo should look like this, but it’s only showing the top part.
---
### Author:  [@cpradio](https://meta.discourse.org/u/cpradio)
#### Post date: [July 23, 2016, 3:37am UTC](https://meta.discourse.org/t/onebox-support-for-new-google-photos/30106/11 "2016-07-23T03:37:04Z")
> [@lrossouw](#):
>
> But I think that’s something wrong on Google’s end.
You would be correct. If you look at the meta tags they generate, it links to a photo that only shows the top portion of the portrait photo
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [October 13, 2017, 5:12am UTC](https://meta.discourse.org/t/onebox-support-for-new-google-photos/30106/12 "2017-10-13T05:12:59Z")
We covered this in another topic, the pain here is that our “onebox any image” code depends on file extension instead of doing a HEAD/GET and pulling out the mime type.
I think we should just bite the bullet here and look at mime types cause it cleans up a bunch of places where this is the case.
(note, slack does this)
---
### Author:  [@omarfilip](https://meta.discourse.org/u/omarfilip)
#### Post date: [March 20, 2018, 6:04pm UTC](https://meta.discourse.org/t/onebox-support-for-new-google-photos/30106/13 "2018-03-20T18:04:00Z")
Seeing how Instagram oneboxing is working nicely, any chance the same could be applied to Google Photos albums?
> [@Instagram oneboxing](https://meta.discourse.org/t/instagram-oneboxing/69099):
>
> Continuing the discussion from [Onebox Twitter embedding](https://meta.discourse.org/t/onebox-twitter-embedding/18943/20): There is an issue with Instagram embedding for which there is no topic to my surprise. I only found this comment by @Apreche written in January. This is actually causing quite a lot of confusion among users. They post an URL to its own line but instead of a link, they see an image in their post. Is there any way to improve this behaviour?
Here is the link that Google produces for sharing an album with 3 photos in it:
[https://photos.app.goo.gl/OPDpevnR0XUHTqA33](https://photos.app.goo.gl/OPDpevnR0XUHTqA33)
And here is how a Google Photos album with 3 photos is presented in Discourse:
[ ](https://photos.google.com/share/AF1QipO8oeS1WeGACM0BPRW5auzqlSg3qvJKPLA9iT7B1iAQ1oPzJWSj5pKcgmHTB8dePw?key=VTlrMXRvUm12d1ZybmVtSkYydENuUVRjV2RRdzZR)
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [March 21, 2018, 4:59am UTC](https://meta.discourse.org/t/onebox-support-for-new-google-photos/30106/14 "2018-03-21T04:59:56Z")
I don’t see that used as much as Instagram, so it isn’t as much of a priority.
---
### Author:  [@techAPJ](https://meta.discourse.org/u/techAPJ)
#### Post date: [November 10, 2018, 6:23am UTC](https://meta.discourse.org/t/onebox-support-for-new-google-photos/30106/16 "2018-11-10T06:23:22Z")
Onebox [now](https://github.com/discourse/onebox/commit/566056a343461432e5606c77b458eab5c89c130d) has a dedicated engine for Google Photos to support album, image and video links. Demo:
Album:
[https://photos.app.goo.gl/pXA7T8zBX4WZWVMT7](https://photos.app.goo.gl/pXA7T8zBX4WZWVMT7)
Image:
[https://photos.app.goo.gl/GrJbrCUDUw6JUUSv8](https://photos.app.goo.gl/GrJbrCUDUw6JUUSv8)
Video:
[https://photos.app.goo.gl/hmqzFFyVHxZ91FCo9](https://photos.app.goo.gl/hmqzFFyVHxZ91FCo9)
---
### Author:  [@ky\_metro](https://meta.discourse.org/u/ky_metro)
#### Post date: [December 20, 2018, 6:23pm UTC](https://meta.discourse.org/t/onebox-support-for-new-google-photos/30106/26 "2018-12-20T18:23:39Z")
That is AWESOME. Thank you!!
---
### Author:  [@danekhollas](https://meta.discourse.org/u/danekhollas)
#### Post date: [April 13, 2019, 8:21pm UTC](https://meta.discourse.org/t/onebox-support-for-new-google-photos/30106/27 "2019-04-13T20:21:47Z")
It seems that the Onebox is cropping the image in my case. Am I doing something wrong?
[https://photos.app.goo.gl/1j3E4exAQUeBSDEn7](https://photos.app.goo.gl/1j3E4exAQUeBSDEn7)
Onebox
[ ](https://photos.google.com/share/AF1QipM0O-LQWRA9QR3sOpHh3muGGpfEsNRM_lIJNplLFK_b1OfXaS3zbrwPvucR0cjflA?key=bkx1YmxLM0I0RTlJcC1rZmxIbzZTVEs1X0JsX05R)
Full image
---
### Author:  [@techAPJ](https://meta.discourse.org/u/techAPJ)
#### Post date: [April 25, 2019, 6:13am UTC](https://meta.discourse.org/t/onebox-support-for-new-google-photos/30106/28 "2019-04-25T06:13:16Z")
Onebox uses `og:image` tag to get image link and in above case the cropped image is what Google is linking to as per:
```plaintext
```
No image cropping is happening on discourse/onebox side.
---
### Author:  [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [December 4, 2025, 11:36am UTC](https://meta.discourse.org/t/onebox-support-for-new-google-photos/30106/29 "2025-12-04T11:36:01Z")