Rivya Browser, Upload, and Playback Requirements
Fix browser, network, file upload, and playback problems in Rivya. Protect drafts before reloading and check task status before submitting the same request again.
Last reviewed on September 9, 2026
Start by identifying where the problem occurs: opening the page, uploading a file, sending the task, or opening a finished result. A browser error is not enough to tell whether Rivya accepted a generation request. Check an existing task before submitting it again.
Set Up the Browser for the Task
Use an up-to-date browser, allow the site's scripts and sign-in session to work, and keep a stable connection while uploading and submitting. Open Rivya directly in your regular browser if an embedded browser inside another app behaves unexpectedly. This is a troubleshooting step, not a guarantee that changing browsers fixes the task.
| Symptom | First check |
|---|---|
| Page or form does not load | Confirm the address and network connection, then check whether an extension is blocking this site |
| Upload or submit asks you to sign in | Check the active account; see sign-in and access |
| A copy button does not copy text | Select and copy the visible text manually; verify the pasted text before leaving the page |
| A result opens in another tab instead of saving | Use the browser's save or download control on that result; see output downloads |
If an extension appears to interfere, temporarily test without that extension for this site and restore your preference afterward. Do not start by clearing all browser data: it can sign you out and does not resolve an unsupported model input.
Protect Your Work Before Refreshing
Copy unsent prompts or chat text to a local note. If a copy button fails, use manual selection and confirm the text was actually saved.
Record the model, operation, settings, and any visible task identifier. Keep the original reference files on your device.
If you already submitted, check History or the correct saved conversation before refreshing or sending again. History and an unsent draft are not the same thing.
Refresh or reopen the page only after preserving this information. Check sign-in, model, settings, and displayed references again; re-upload the prepared files if needed. Follow login and draft protection when signing in changes the page.
A different browser or device does not automatically receive your unsent text, selected local files, or every setting. A saved task or conversation must belong to the account you use to open it.
Check the File Against the Selected Operation
Check model availability and reference-file requirements before changing browsers. Type, size, count, dimensions, aspect ratio, duration, and supported combinations depend on the model and mode. A file that opens on your device can still be invalid for that operation.
Open the original locally to check that it is readable. Export a separate copy in an accepted format when conversion is needed; renaming the extension is not conversion. Reducing size must not break a minimum dimension or other requirement. Prepare the copy with the safe-upload guide before sending it, and wait until upload completion is confirmed in the form.
The current chat attachment picker accepts JPEG, PNG, and WebP images when the model supports images; it is not a general PDF, spreadsheet, audio, or video uploader. For recording-based work, read audio uploads rather than assuming a speech-generation model edits an existing recording.
Separate Connection Errors from Task Status
The generation form checks a running task periodically. A failed network request can interrupt those updates; an unchanged page is not proof that the task stopped. A lost response when sending can also leave you unsure whether the request was accepted.
Restore the connection and check the existing task. Use queue and waiting guidance for an in-progress task and failed tasks and credit returns for a recorded failure. Do not infer failure, cancellation, a refund, or a completion time from a browser message alone. A second submission can create another task with its own credit cost.
Retry a missing upload after checking which files are already displayed. Retry a generation only after checking the earlier request and resolving the reported issue. Change one relevant input at a time; making every file smaller or rewriting the entire prompt can hide the original cause.
Open and Save Finished Results
Use the available result link, check that the full file opens, and save a local copy if you need it. In History, the download action opens the primary output in a new tab; the browser may display the file before you save it.
For video or audio that will not play, try the downloaded file in a compatible player if the link still works. Playback support depends on the media format and encoding, so an MP4 extension alone is not a complete compatibility check. The MDN media-format guide explains that distinction.
An expired or unavailable result link is different from an unsupported player. Follow the download guide for retention and expired-output handling. Do not create a paid replacement just because a preview fails before checking whether the existing file can be opened. Review image dimensions, sound, duration, and editing needs before using the result.
Send Useful Details When You Need Help
If the problem persists, follow troubleshooting or use Contact. Include the page or model, browser and version, device, approximate time, exact visible error, and task identifier if available. For file issues, add format, size, relevant dimensions or duration, and the point where the process failed.
A cropped screenshot without private details can help. Do not share passwords, API keys, verification codes, raw session data, or private media access links. State whether the task appears in History and what you already tried so the next check can target the actual failure.