> For the complete documentation index, see [llms.txt](https://thecontentforge.gitbook.io/thecontentforge-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thecontentforge.gitbook.io/thecontentforge-docs/feature-guides/publishing.md).

# Publishing

The Publish Panel lets you send, schedule, or manually log generated posts from Content Forge and Video Forge. No copy-paste, no leaving the platform.

### Requirements

* A connected account for the target platform; see [My Account > Social Connections](https://thecontentforge.gitbook.io/thecontentforge-docs/feature-guides/social-connections.md)
* The profile must be marked as **Publish** in My Account > Social Connections
* If your org has the **Approval Workflow** enabled, posts route through approval before publishing

Manual logging does not require an active OAuth profile. It records that you already posted the item elsewhere.

### Who can send immediately

* **Owners/Admins** manage the connections and decide which profiles are publishable
* If approval workflow is **off**, any user can publish through an already-connected publishable profile
* If approval workflow is **on**, whether a user can send immediately depends on the configured minimum approver role

### Publish, schedule, or log

After generating in Content Forge or Video Forge:

1. Open the Publish Panel on the output card
2. Pick the platform and connected profile when publishing or scheduling
3. Edit the final text if needed
4. Optionally attach media (images or videos)
5. Choose **Post now**, **Schedule post**, or **Already posted it yourself**
6. Submit

Scheduled posts appear on the [Calendar](https://thecontentforge.gitbook.io/thecontentforge-docs/feature-guides/calendar.md) and publish automatically at the specified time via a background job.

If you post manually outside TheContentForge, the next analytics sync can fetch or match it. You can also log it manually from the Publish Panel after generating in either studio so it appears on the Calendar immediately.

### Media attachments

* Click the attach button below the textarea to pick an image or video
* Uploads run **on submit**, not when you pick the file, so nothing is uploaded unnecessarily
* If a submit fails, the retry reuses the already-uploaded asset; you do not re-upload
* Attached media is stored privately, scoped to your org, and shared only at publish time
* Ephemeral uploads are cleaned up 24 hours after the post publishes

### Carousels and Stories

Every workspace, in any vertical, can publish a carousel or a Story from the same Publish Panel, next to a single post. Under the post text, **Format** offers:

* **Single post**: text with up to one image or video, on any network (as before)
* **Carousel**: 2 to 10 images in one post, in your order, on Instagram, Facebook (a multi-photo Page post) and LinkedIn (a multi-image post)
* **Story**: 1 to 10 frames shown one after another, without a caption, on Instagram (images or videos) and Facebook Page Stories (photos only)

Format is not offered for an X thread or for a locked campaign piece (resort pieces use their own carousel and Story frames flow), and not while carousels and Stories are switched off.

**Choosing media.** With Carousel or Story chosen, **Add from Asset Library** opens the library. Choose items in the order they should appear; each choice is added at the end. In the list, **Move up**, **Move down** and **Remove** set the order (keyboard accessible). Items the publisher would refuse are shown with the reason and cannot be added: not reviewed as Safe for content, the file no longer stored, past its rights or expiry date, or blocked by its rights (do not use, rights status, publication withheld, commercial use, missing credit line). Media used recently elsewhere is listed last with the date it was used, under the workspace's Avoid reusing media setting; it can still be chosen.

**Rules before scheduling.** Under the list, each picked network shows its rules and what still stops the selection:

| Network            | Carousel                                                                                                                                                   | Story                                                                         |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
| Instagram          | 2 to 10 images, between 4:5 and 1.91:1; every image is cropped to the shape of the first. PNG, WebP, GIF, BMP, TIFF and HEIC are converted to JPEG for you | 1 to 10 images (converted the same way) or MP4/MOV videos, no caption or link |
| Facebook           | 2 to 10 JPEG, PNG, GIF, BMP or TIFF photos, posted as one Page post                                                                                        | 1 to 10 photos (no video), no caption                                         |
| LinkedIn           | 2 to 10 JPEG, PNG or GIF images, one multi-image post                                                                                                      | not offered                                                                   |
| X, Threads, TikTok | not offered                                                                                                                                                | not offered                                                                   |

Networks that do not take the chosen format cannot be picked; the panel says so ("We do not publish carousels to X, Threads, TikTok"). The button stays off, with the first reason beside it, until the selection fits every picked network. The post text is the caption of a carousel; a Story publishes no text (it is kept with the post in the Calendar).

**Sending.** Post now, Schedule and I posted it myself work as for a single post: one scheduled post per network, with every media item in order and the format recorded on the post (`platform_options.media_format`). The approval workflow, connected accounts, who may publish and the per-network publishing gates are the same as for a single post. When the post goes out, the publisher checks every item again (in this workspace, Safe for content, stored, inside its dates, cleared by the shared rights gate) and the selection against the network's rules, and refuses the whole post with a plain reason rather than publish one image. The database refuses a carousel or Story outside resort campaigns whose network, count, image or video kinds, workspace, review or rights dates do not fit (`20261119150000_multi_media_all_workspaces.sql`).

**Instagram and JPEG.** Instagram takes JPEG images only, but Content Forge and Image Forge make PNGs and most libraries hold PNG or WebP. So before an Instagram post goes out (a single post, a carousel or a Story), each PNG, WebP, GIF, BMP, TIFF, HEIC or HEIF image is turned into a JPEG copy on the server (the image worker) and Instagram is sent the copy. The panel says "Instagram takes JPEG images. Other image types are converted for you." and lists which items will be converted. The copy keeps the whole picture: turned the right way up, transparency laid on white (or on black when the visible picture is almost white, as a light logo made for dark backgrounds is), sRGB colour, quality 95, no camera or location details, no wider than 1440 pixels (Instagram's own limit). A GIF goes as a still picture of its first frame. The original is never changed, and Facebook, LinkedIn and every other network are sent the original as before.

The copy has no rights of its own and is not an Asset Library item: it is used only after the original passes every check above, and it is deleted when the original changes, is deleted, is marked do not use, loses its Safe for content review, has publication withheld, or passes its rights or expiry date; one unused for 60 days is deleted too and made again when needed. Media whose licence forbids keeping a copy (no store) or any change cannot be converted; the panel and the database refuse it for an Instagram carousel or Story, and the publisher refuses a single post with it. If a copy is still being made when the post is due, the post waits in the queue (at most ten minutes); if it cannot be made, the post fails before anything is sent to Instagram (so a carousel is never posted in part), the Calendar names the image and the reason, and **Retry** tries the conversion again (`20261119160000_instagram_jpeg_copies.sql`).

**Stories publish frame by frame.** Progress is saved after each frame. If a frame fails, the Calendar says how many frames are live and which frame was refused; **Retry** on the post publishes only the frames that are not live yet. A carousel or multi-photo post is all or nothing: nothing is visible until the whole post is accepted.

**Switching it off.** Carousels and Stories are on for everyone by default. To switch them off without a deploy, set the `media_runtime_config` row `multi_media_publish_enabled` to 0 (see [Resorts](https://thecontentforge.gitbook.io/thecontentforge-docs/feature-guides/resorts.md#carousels-and-story-frames) for the statement). Within a minute the panel stops offering the formats and the publisher refuses any carousel or Story with "Carousels and Stories are switched off right now, so nothing was published"; nothing else changes. An environment value of `false` in `MULTI_MEDIA_PUBLISH_ENABLED` (or the older `RESORT_MULTI_MEDIA_PUBLISH_ENABLED`) also forces it off for that runtime.

### Threads (X)

When Content Forge returns an X thread (Thread mode or **Summarize the project**), the Publish Panel switches to a per-tweet editor. Every tweet in the thread is available for all orgs, not just Web3 projects.

* Edit each tweet in place - edits are preserved while the Publish Panel is open and never reverted by background re-renders
* Add or remove tweets with the **+ Add tweet** / trash buttons
* Each tweet has its own media controls:
  * **Attach** - upload an image or video for that specific tweet
  * **Generate** - create a headline image for that tweet with AI
  * **Brand asset** - (Web3 Project orgs) pick a logo, icon, template, or any asset you marked **Safe for content** in the [Asset Library](https://thecontentforge.gitbook.io/thecontentforge-docs/feature-guides/asset-library.md)
* On submit, the panel creates one scheduled post per tweet, grouped as a single thread and kept in order
* Publishing chains the replies natively on X; if any tweet in the chain fails, later tweets do not publish
* Instagram and Facebook receive a single concatenated post (thread semantics do not apply on those platforms) with the first tweet's media attached

**Platform specifics:**

* **X** - images and video are supported on posts and on each tweet of a thread
* **Facebook and Instagram** - a thread is posted as one combined post with the first tweet's media; use **Carousel** or **Story** (above) for several images in order

### Attach to Experiment

The Publish Panel has a collapsible **Attach to experiment** section. Expand it to pick one of your active or draft [Experiments](https://thecontentforge.gitbook.io/thecontentforge-docs/feature-guides/experiments.md) and assign the post to a specific variant. The experiment list is filtered to the platform you're publishing on, so you only see experiments that can actually receive the post.

* Attaching a draft, scheduled, or post-time publish all work - the attachment is created when the post saves
* Once published, the post is auto-linked back to the experiment, so you do not need to reattach after publishing
* Posts without an attachment are unaffected - the section is fully optional

### Approval workflow

When approval is enabled in Settings:

1. A scheduled or publish-now post enters an Approval pending state
2. A user at or above the configured min role (Editor, Admin, or Owner) approves or rejects it from the [Calendar](https://thecontentforge.gitbook.io/thecontentforge-docs/feature-guides/calendar.md)
3. Approved posts move to Queued and publish at the scheduled time
4. Rejected posts are marked accordingly and do not send

### Failure handling

If a publish attempt fails (platform error, expired token, media rejected), the event's status flips to Failed and the error message surfaces on the event drawer. For a carousel or Story the drawer says in plain words what happened and which frame, and an owner, admin or editor can choose **Retry** to put the same post back in the queue; a post that is already due goes to the publisher at once. Non-fatal warnings, such as a platform caveat after publishing, land in **Publish notes** so they do not get confused with hard errors.

### Related

* [Content Forge](https://thecontentforge.gitbook.io/thecontentforge-docs/feature-guides/content-studio.md) - Where text posts are generated
* [Video Forge](https://thecontentforge.gitbook.io/thecontentforge-docs/feature-guides/video-studio.md) - Where video-derived posts are generated
* [My Account > Social Connections](https://thecontentforge.gitbook.io/thecontentforge-docs/feature-guides/social-connections.md) - Connect accounts to publish through
* [Calendar](https://thecontentforge.gitbook.io/thecontentforge-docs/feature-guides/calendar.md) - Track scheduled, pending, manual, and published posts
