Skip to content
Stago Docs

Search by task, feature, or question.

Use ↑ ↓ to move through answers · Enter to open
Open Stago

Fix upload and preview problems

Start with the error shown in the upload area. Keep the original file until the upload, processing, and review preview have all succeeded.

Check the accepted formats and selected stage type. A renamed extension doesn’t convert the file’s contents. Document upload accepts PDF, DOC, and DOCX; use the Collaborative Editor for writing directly in Stago.

Check both the workspace plan and the content-specific limit. Available storage can stop an upload even when the individual file is small enough. For an organization project, look at the owning workspace’s allowance.

Confirm the connection is stable and the account still has upload access. Follow Retry or Resume if the current uploader offers it. Where video resume requests the original file, select that same source rather than another revision.

Avoid launching repeated copies of the same upload. Check whether an attempt already completed before starting again. For a gallery or track list, inspect each item and retry the failed item; successful items don’t need to be uploaded again.

Upload finished but the preview isn’t ready

Section titled “Upload finished but the preview isn’t ready”

Transfer and processing are separate steps. Video may need preview processing; audio may need waveform generation. Wait for the status to change, then open the paired review and select the correct draft.

DOC/DOCX intentionally use download rather than inline Word preview. PDF display depends on the browser. An external link can require permission in the source service.

Check stage state and your role. A locked dependency, an approved project, or a read-only account can prevent changes. A client also needs a visible upload stage and a link allowing upload.

Viewing doesn’t automatically grant download. Ask the owner to review that permission rather than forwarding another person’s link.

Use the feedback control in Settings when available. Include the content type, file size, approximate time, browser, the action that failed, and the visible error. A screenshot can help, but hide client material and private account details. Never include a password or integration token.