Source word limits

What the source limit applies to

The source is the Markdown you upload or paste before generating channel versions. Its allowance is separate from the length accepted by a destination and from the AI credits available to your workspace. A source that fits does not guarantee that every generated version fits its destination.

Use the allowance shown in your current workspace or the validation message returned when submitting a draft. Early-access pricing is still being finalized, so this guide does not promise a fixed word allowance for every account.

Before uploading a long draft

• Keep a copy of the full original before shortening it.
• Choose one main topic and identify the audience and intended outcome.
• Remove duplicated introductions, repeated appendices, and copied navigation text.
• Keep citations, code required for the example, and qualifications that change the meaning.

If the source is rejected

1. 1

   Read the validation message

   Confirm whether it concerns word count, file type, or another field. A generation failure is not necessarily a source-length problem.

2. 2

   Shorten deliberately

   Remove repetition first. If the document contains independent subjects, create separate sources that each make sense on their own.

3. 3

   Submit the revised source

   Check the active workspace and use its current allowance. If a comfortably shorter source still fails, keep the error message and contact support.

Preserve meaning when splitting content

A setup tutorial should retain its prerequisites and working example. A product announcement should retain the limitations attached to its claims. Splitting either at an arbitrary word boundary can produce a draft that is shorter but misleading.

For example, a release note covering three unrelated products may become three sources. Each should name its product, explain the change, include its relevant limitations, and link to the full release note. A single troubleshooting procedure usually needs its complete sequence in one source.

Check destination versions separately

Review generated articles and social posts for the destination’s format and length constraints. Shortening the source is not a substitute for reviewing an output. Keep the source URL or canonical attribution where appropriate, and confirm the selected channel’s publishing method.

For allowance questions, contact the team with the workspace, approximate source length, and exact validation message. Do not include credentials or confidential source content in the support request.