Rivya Browser and File Requirements

Use this guide before a Rivya task depends on an upload, reference file, generated output, or unstable browser session.

Browser behavior, file size, format, network conditions, and unsupported inputs can affect whether a task starts, finishes, or returns an output you can reuse.

Browser Expectations

Use a modern browser with a stable network connection.

If something does not load or submit correctly, try:

• refreshing the page

• checking sign-in status

• confirming network access

• disabling aggressive browser extensions

• trying a supported modern browser

• returning through history or notifications if a task already started

Avoid submitting duplicate tasks until you know whether the first one was accepted.

File Upload Expectations

Before uploading a file, check:

• file format

• file size

• whether the file is corrupted

• whether the content is actually needed

• whether the task supports that input type

• whether the upload finished before submitting

If an upload fails, retry with a smaller or simpler file when possible.

Generated Output Files

Generated outputs should be reviewed before use.

Check whether the file:

• opens correctly

• fits the intended placement

• needs editing

• should be downloaded now

• should remain in history for continuation

Use Downloading and Using Outputs for post-generation handling.

When To Retry With Simpler Inputs

Try simpler inputs when:

• the file is large

• too many references are used

• the prompt has too many constraints

• the task keeps failing

• the output is drifting unpredictably

A simpler first run is often easier to diagnose.

Upload And File Checklist

Before a task depends on a file, reference, or provider handoff, check:

• Check file type, size, source quality, and whether the workflow actually supports uploads.

• Decide whether the file is a reference, a source to transform, or material for analysis.

• Remove sensitive or unnecessary data before upload.

• Check provider-processing expectations if the file leaves the browser as part of generation.

• Keep the original file available until the generated result has been reviewed.

The goal is to make the input safe and useful before generation starts.

When File Inputs Need Rework

Rework the input when the upload is too large, too noisy, too sensitive, unsupported by the chosen workflow, or unclear about what it should control.

In those cases, fix the file or choose a better workflow before spending credits on a generation attempt.

Related Pages

• Troubleshooting in Rivya

• References and Uploads in Rivya

• Safe Upload Guidelines

• Audio Uploads in Rivya

• Failed Tasks and Credit Refunds

• Generation Queue and Waiting Times