If you have a webshop and want to use Bynder images on your website, those images need to be public and retrievable through the API. You may also want to make some of your assets public, visible and downloadable to all. We can help you setting up your portal in a way that public URLs will no longer be accessible when you archive the public assets.
For information on creating public collections, see Create, share and manage collections.
If your files are not public, they are private, which means that users who are not logged in cannot see or download them.
Contact your Customer Success Manager if you would like to have this feature enabled for your portal.
Select one or more images in the asset overview and edit them, or click an asset and click the Edit tab on the Asset detail page.
Expand the Advanced Rights tab.
Select Mark as public. When an asset is marked a public a publicly accessible URL is created for this asset. Any user who has the URL can then view and download the asset.
Making an asset public allows external users to open the asset link if you share the link with them. If you decide to make a file public, you will not be able to clear the checkbox and make it private again. You can only delete or archive a public file.
If your public files are served through our CloudFront CDN, their link can refresh real-time. For example when you upload a new version of the file, the link can get updated so that the latest version automatically displays on your external website. Read more about our automatic invalidation process here.
Thumbnails and webversions are public by default. To change this, see Share thumbnails in a more secure way.
Marking an asset as public makes the original asset public. The URLs to view the original image and the derivatives can now be retrieved via the API. If you want only specific derivatives to be public contact your Customer Success Manager or Onboarding Manager for help with the setup.
Do you no longer want your asset to be publicly available?
We can set up your portal so that public URLs are no longer working when an asset is archived. Read more about it here.
Currently public links are build up with the following formats:
The /m/ element indicates that it is a public link.
The idhash is a randomly generated hash based on the mediaID. It's a 16-character hexadecimal string.
This indicates that the URL links to the original file.
This is a mandatory reference to determine which derivative of the asset to use
This value represents the name of the asset.
The file extension of the original file or derivative.
Did you know?
Enforce a download by placing ?download behind the public URL. Upon opening the public URL the asset will be downloaded directly instead of viewed.
You can customize your public URLs for SEO optimization or meeting the naming conventions of your brand. Any text behind the /original/ or derivative-prefix- element can be replaced with your own text. Based on the random idhash the system can still redirect users to the correct public original file or public derivative.
The two public URLs below link to the original file and to the 'socialmedia' derivative. This is the default non-customized version of both URLs
Optionally, the text behind the orginal and socialmedia- elements can be fully removed or customized. You can make the changes in your preferred text editor. The following URLs could for example also be used:
You cannot make the URL customizations in the portal itself. The changes can also not be saved to the portal.
By default, public derivatives are only accessible through the API and are not visible to users on the Asset detail page. If you want to make them visible, contact your Customer Success Manager or Onboarding Manager.
By default, the public URLs of an asset will still be accessible when the asset is archived. If you don't want this to be the case, we can set up your portal so that public URLs are no longer working when an asset is archived.
Contact your Customer Success Manager if you would like to have this configuration enabled for your portal.
Public URLs of an asset that have been visited recently are most likely cached. Archiving an asset doesn't invalidate the public URLs. This means that even when you archive a public asset the cached public URL(s) will remain accessible until the cache has expired.
The default expiry time of our CDN offered by Amazon Web Services (AWS) is 24 hours. In case you make use of a custom CDN the public URLs will no longer work when your custom expiry time has expired.
When you delete a public asset the public URLs will no longer be accessible. In case the public URLs have been cached the URLs will remain working until the cache has expired. The default expiry time of our CDN offered by Amazon Web Services (AWS) is 24 hours. In case you make use of a custom CDN the public URLs will no longer work when your custom expiry time has expired.
You can retrieve your assets via the API. By default, the URLs to view the derivatives of image assets will be returned by the API. When you visit this type of URL the derivative will be displayed in the browser. If your marked the assets as public the link to view the original image file will also be returned. These 'viewing' links are valid permanently. You can find more information about this type of API call here.
If you want to offer your users a link to download original image assets or their derivatives you can also retrieve download URLs via the API. These download URLs expire after 6 hours. Read more about this API call here.
Do you have public assets or and do you want to know whether they can be indexed by search engines. Read more about it here.