How files behave in Kuse
Understand the difference between recognizing, uploading, previewing, editing, using, generating, and downloading a file.
“Supported” does not mean every file type behaves in the same way. Check the exact action you need before designing a larger workflow around a format.
File actions are separate capabilities
| Capability | What it means | What to verify |
|---|---|---|
| Recognized | Kuse identifies the extension or file category. | The file appears with the expected type after upload. |
| Uploaded | The file can be added to a Project or task. | The upload finishes and the file remains available. |
| Previewed | Kuse can show the file in a viewer. | Important pages, sheets, media, or formatting are visible. |
| Edited | The current workspace offers an editing surface. | The change can be saved and reopened correctly. |
| Used as context | Kuse can use information from the file in a task. | A known fact from the source appears accurately in the result. |
| Generated | Kuse can create a result in that category or format. | The generated result opens and contains the expected structure. |
| Downloaded | The result or source can be exported. | The downloaded file opens in the intended external application. |
Behavior can vary inside one category
Two spreadsheet or media extensions can have different preview and editing behavior. File size, encoding, protection, embedded content, and browser support can also affect the experience.
Test the real operation
- Upload a safe example that resembles the real file.
- Open it and check the information you need.
- Run a small task using one known fact.
- Download the result if export is part of the workflow.
- Repeat after a major product or file-format change.