# Twitter/X Long-Form Posts

Unlock the ability to schedule and publish long-form posts (up to 25,000 characters) to Twitter/X using the Publer API—exclusively for accounts with an X Premium subscription.

### Overview

Twitter/X supports long-form posts (sometimes called "long posts" or "extended tweets") for users with an X Premium (formerly Twitter Blue) subscription, even at the Basic tier. These posts can contain up to **25,000 characters**, far exceeding the standard 280-character limit.

With Publer, you can programmatically schedule and publish long-form posts via the API. Publer automatically detects your account’s eligibility and switches to the appropriate post type.

### How It Works

* **Accounts with X Premium:**\
  You can create and schedule long-form posts up to 25,000 characters.
* **Accounts without X Premium:**\
  Your post text will be truncated to the standard 280-character limit, and the long-form post type will be disabled.

> **Tip:** Validate the post length in your integration to avoid surprises when publishing.

### Key Differences

* **Long-form posts** are not the same as Twitter threads. Threads are multiple connected posts; long-form posts are a single post with expanded character count.
* Scheduling long-form posts is not possible directly on X/Twitter—use Publer’s API or platform to achieve this functionality.

### Request Example

To schedule a Twitter/X long-form post, set the network type to `"long_post"` inside the `details` object for the `"twitter"` network:

```json
{
  "bulk": {
    "state": "scheduled",
    "posts": [
      {
        "networks": {
          "twitter": {
            "type": "status",
            "details": {
              "type": "long_post"
            },
            "text": "This is a twitter long post"
          }
        },
        "accounts": [
          {
            "id": "66e011b94e299eb49376c715",
            "scheduled_at": "2025-09-24T14:16+02:00"
          }
        ]
      }
    ]
  }
}
```

<table><thead><tr><th width="285.07891845703125">Field</th><th width="71.5963134765625">Type</th><th>Description</th></tr></thead><tbody><tr><td><code>networks.twitter.details.type</code></td><td>string</td><td>Must be <code>"long_post"</code> for long-form posts</td></tr><tr><td><code>networks.twitter.text</code></td><td>string</td><td>Content of your long-form post (max 25,000 characters with X Premium)</td></tr></tbody></table>

### Important Notes

* **X Premium Required:** Only X Premium accounts can publish long-form posts. For other accounts, posts will be truncated to 280 characters.
* **Not for Threads:** Use this format for single extended posts, not for multi-part threads.
* **API Detection:** Publer automatically detects account eligibility for long-form posting.
* **Scheduling Limitation:** Twitter/X doesn’t natively support scheduling long-form posts; this is enabled via Publer’s platform and API.

### Best Practices

* Check your account’s X Premium status before relying on long-form functionality.
* Always validate post length to ensure your content is not unintentionally truncated.
* Use long-form posts for in-depth announcements, articles, or detailed updates—threads remain better for sequential storytelling.

### Related Topics

* [Content Types Overview](/docs/posting/create-posts/content-types.md)
* [Publishing Methods](/docs/posting/create-posts/publishing-methods.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://publer.com/docs/posting/create-posts/content-types/platform-specific-formats/twitter-x-long-form-posts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
