Bluesky text posts work but video fails: check email verification first

Video has an account prerequisite that text does not prove

Bluesky's official video tutorial says its video service applies account-level limits and requires Bluesky-hosted accounts to have verified their account email. A healthy text-posting session therefore does not rule out a video-specific eligibility issue. Start with the exact error and the account selected in your publisher before changing the clip's format or repeatedly reconnecting the integration.

The scope matters: the documentation specifically identifies Bluesky-hosted accounts. Do not turn that into an unsupported claim about every independent hosting arrangement. If you use a different provider, check that provider's current requirements and the destination service involved. For ordinary troubleshooting, the first useful question is which account and hosting path are actually attempting the video upload.

Confirm verification on the intended account

Open the account's native settings and follow the current email-verification process if it is incomplete. Make sure you are checking the same account connected to the publisher, especially if you manage several handles. Complete the verification through the legitimate account flow, then return to the publishing workflow. A different account's verified address does not establish the state of the selected identity.

For developers and support teams, Bluesky documents checking verification status through com.atproto.server.getSession. Creators do not need to extract or share authentication tokens to report the problem. Provide the handle or public account identifier, approximate attempt time, and exact message instead. If the verified state is not recognized, ask support to inspect the selected session and account mapping rather than guessing at file changes.

1. Confirm the exact destination handle and whether the account is Bluesky-hosted.
2. Check and complete email verification through the native account settings.
3. Review the exact video error and any current upload-allowance message.
4. Retest once with a small, harmless clip you own through the supported route.
5. If it still fails, preserve the job identifier and distinguish transfer from processing failure.

If verification is complete, follow the next diagnostic branch

Email verification is a prerequisite, not a universal diagnosis. Bluesky also documents limits on video posting and a processing lifecycle distinct from text creation. Check the current allowance and the actual error before assuming the same remedy applies to every failure. Do not invent a fixed daily quota from an old article; the relevant service and account conditions can change.

The video tutorial explains that a simple upload can create a post before its video finishes processing, while the recommended preprocessing flow waits for a blob reference first. If text is visible but the video is not yet ready, inspect the existing operation rather than creating another copy immediately. A temporary processing state should not be treated as proof that verification failed again.

Send evidence that separates account and media problems

Record whether text posting works, whether the account is verified, which video allowance or error is shown, and whether a public post already exists. Add the file's duration, dimensions, and size when the error concerns media. Keep a copy of the original clip for a controlled comparison, but do not send private footage or credentials in a public support thread.

If you use Ferryman, confirm the Bluesky identity in the flow that failed and inspect that flow's result. Changing an unrelated origin connection will not prove the destination prerequisite is satisfied. After a successful recovery, inspect the video itself and preserve its URL. The useful conclusion is narrow: this account and this route completed the intended post, not that every future video failure has the same cause.