Handle unsupported media in the desktop app
When desktop preview cannot render a media file, use Download, open the saved copy in a compatible app, and confirm the cloud object stays unchanged.
Last reviewed
An inline preview can fail even when the stored file is intact. Download the object through Dosya, then open that saved copy in an application that supports its codec or format.

Before you start
Confirm the selected file’s name, extension, size, and workspace. Your role must include download_files; without that permission, the recovery action is unavailable even though you can see file metadata.
The viewer can show This file type cannot be previewed. Download it instead. Office conversion, video decoding, and audio decoding also have their own fallback messages. Text files larger than 2 MiB are not previewed inline, and syntax highlighting is limited to 300 × 1024 UTF-16 code units.
Steps
- Open the media file in the desktop viewer and record the exact preview or decode message instead of assuming the stored bytes are corrupt.
- Compare the unsupported media extension and size with the source or expected Dosya upload receipt.
- Select Download in the desktop viewer and choose a trusted local destination in the save dialog.
- Wait for the Downloaded toast, note the displayed path, and use Show in Folder if needed.
- Open the saved copy with a compatible local application and test the media, document, or text content.
- Return to Dosya and confirm the original cloud path and metadata remain unchanged after the download.

A successful download is non-destructive: it creates a local copy and does not change the cloud object. The desktop app does not expose an Open with action for this fallback; opening externally happens after saving.
Expected result
The saved local copy opens in a compatible application and matches the expected file. The cloud item remains at its original path because downloading does not move, rename, or delete it.
If the toast says Download failed, verify download_files, available disk space, and connectivity. A file that also fails in an independent application may need a fresh upload from a known-good source.
Related guides
Was this helpful?
Loading helpfulness results…
Voting saves a necessary ballot cookie for up to 180 days so you can change your answer.
Questions and replies
Ask about the steps in this guide. Questions are reviewed before publication.
Keep account details, credentials and private files out of public questions. Use private support for those.
Loading questions…
Sign in to your Dosya account to ask a question.