# Public urls for images
**URL:** https://community.fibery.io/t/public-urls-for-images/3838
**Category:** Ideas & Features
**Created:** [January 23, 2023, 6:06am UTC](https://community.fibery.io/t/public-urls-for-images/3838 "2023-01-23T06:06:20Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@tpaktop](https://community.fibery.io/u/tpaktop)
#### Post date: [January 23, 2023, 6:06am UTC](https://community.fibery.io/t/public-urls-for-images/3838/1 "2023-01-23T06:06:20Z")
I noticed that rich text fields can be queried using GraphqlAPI as HTML. Which is a perfect case to make Fibery into a small CMS.
However, images embedded within text apprear to be fixed to fibery account and I couldn’t find a easy way to download them.
Here is example that I get:
```auto
html: 'Building Websites is Like Building Trust in Your Team.
It takes time.
',
__typename: ‘RichField'
```
As you can notice the `img` tag has attribute `src` which points to relative url. This url works only within Fibery context and I haven’t found a way to get it available publicly - even when url is prepended with my workspace url.
The only workaround I have found is the following:
1. Share specific entity publicly.
2. Extract `?sharing-key=XX` from entity.
3. Modify returned images `src` attribute to prepend workspace url AND add sharing key.
Would be great to avoid this workaround and being able to get public url for embedded images using Graphql API.
---
### Author:  [@Eren\_Turgut](https://community.fibery.io/u/Eren_Turgut)
#### Post date: [January 24, 2023, 1:34pm UTC](https://community.fibery.io/t/public-urls-for-images/3838/2 "2023-01-24T13:34:09Z")
Agree, that would probably also fix the issue that when sharing a workspace, all images within rich text fields are lost.
---
### Author:  [@Viktar\_Zhuk](https://community.fibery.io/u/Viktar_Zhuk)
#### Post date: [January 31, 2023, 11:00am UTC](https://community.fibery.io/t/public-urls-for-images/3838/3 "2023-01-31T11:00:10Z")
Hi,
As far as I know we have no other way to share files to the web.
Also instead of this workaround you may store images in some other places like s3 or google drive and insert public url from those stores into the doc. In that case you will be able to see those images in the fibery and can get a document content with direct urls to your publicly hosted images.
---
### Author:  [@tpaktop](https://community.fibery.io/u/tpaktop)
#### Post date: [January 31, 2023, 2:16pm UTC](https://community.fibery.io/t/public-urls-for-images/3838/4 "2023-01-31T14:16:26Z")
They would embed automatically? Didn’t know that.
---
### Author:  [@Edan](https://community.fibery.io/u/Edan)
#### Post date: [March 17, 2025, 2:48am UTC](https://community.fibery.io/t/public-urls-for-images/3838/5 "2025-03-17T02:48:27Z")
Before I go the Google Drive/S3 route, has there been any progress on this?
---
### Author:  [@Chr1sG](https://community.fibery.io/u/Chr1sG)
#### Post date: [March 17, 2025, 2:17pm UTC](https://community.fibery.io/t/public-urls-for-images/3838/6 "2025-03-17T14:17:13Z")
> [@Edan](#):
>
> has there been any progress on this?
no updates
---
### Author:  [@helloitse](https://community.fibery.io/u/helloitse)
#### Post date: [March 17, 2025, 4:07pm UTC](https://community.fibery.io/t/public-urls-for-images/3838/7 "2025-03-17T16:07:26Z")
It would be great if embeds from external sources had a smoother experience. Like the ability to paste the google drive url and have Fibery via an integration get the public url and display it as an embed based on a popup dialog, similar to how Fibery links are converted to mentions.