Postly Cloud gives teams a durable place to store and reuse publishing assets. It matters because campaign speed improves dramatically when media is already in the publishing system instead of scattered across temporary tools.
What Postly Cloud is good for
- reusable campaign images
- evergreen videos
- client asset libraries
- bulk-posting media references
- draft and scheduled post attachment
- API and MCP media ingestion targets
Upload in the dashboard or import through the API
Upload files in the dashboard and reuse them from Postly Cloud. API and MCP integrations can also import public URLs, base64, or data URLs and attach media when creating or updating posts. A local file path alone does not upload a file: the calling client must send its bytes or an accessible URL.
Why this matters operationally
When media is already stored in Postly:
- scheduling becomes faster
- recurring workflows are cleaner
- bulk posting is easier to manage
- AI-generated assets can move into durable storage
- teams spend less time chasing missing files
Recommended media strategy
For regular schedulers
Keep frequently reused assets in Postly Cloud so common campaigns do not require repeated uploads.
For developers
Use the API to ingest media in the format your system already has, then attach the stored result to the publishing workflow.
For AI workflows
If an AI client already has the asset, pass it directly into Postly during the same request flow or agent turn whenever possible.
Organize and reuse assets
Create folders to separate brand assets from campaign working files. Select a stored asset when preparing a post, or copy its Postly Cloud link for a supported URL-based workflow. Keep the source asset available while scheduled or recurring posts still need it.
Deleting a file is not a way to recall live social posts. Some published destinations retain their own media copy, while links and other uses may still depend on your hosted file. Check those dependencies before removing an asset. See Content management to remove published posts.
What to watch for
- broken or expiring public URLs
- mismatched assets across workspaces
- oversized or unusually complex media payloads
- temporary generated references that disappear before post creation
Image thumbnail or preview is blank
If an attached image appears blank in the editor or post preview, try the same image in a new post using another browser. A blank preview alone does not establish whether a cloud upload succeeded or failed.
Reported Chrome behavior on Linux
As of October 16, 2026, we have received a report of blank image thumbnails and Facebook previews in Google Chrome and the installed Postly app on a computer running Kubuntu 26.04 LTS, KDE Plasma 6.6.6, and Wayland. The same image and Postly account displayed correctly in Firefox on that computer. The supplied image also displayed correctly in a separate Chrome test on Windows.
The underlying cause has not been confirmed. This report does not mean that all Linux or Chrome installations are affected, or that the image or account is faulty.
Continue working in Firefox
- Open Postly in Firefox and sign in to the same account and workspace.
- Create a new post and attach the original image. Check both the editor thumbnail and the selected destination's preview before scheduling.
- Keep your existing draft and original file. A draft marked Saved on this device may not be available in another browser; preserve its text separately if needed. Avoid clearing browser data or uninstalling the app as a first step.
Firefox worked in the reported case and is the recommended workaround if you encounter the same symptoms. Changing graphics drivers or advanced browser settings is not required to try this workaround.
Future browser, operating-system, or graphics-stack updates may change the behavior, but no specific update is confirmed to resolve it. After routine stable updates, you can retry Chrome with a new test post without publishing it. Continue using the browser that works for you until you have verified the preview.
If the image remains blank in Firefox too, contact support with the original image, your operating system and browser version, and whether the problem affects other images.