Browse your files
The Files tab shows your data as folders. There are two root spaces, and they follow different rules: one is written by the platform, the other by you.
The two spaces
My Jobs
Every job you create gets a folder here automatically. Inside it:
- Inputs — everything attached to the job at submission.
- Outputs — appears once the job has run, when results sync back from the cluster.
Once a job has run, you cannot upload into its folder. The folder is a record of what that job actually used and produced, and keeping it fixed is what makes results reproducible.
To build on a job's output, promote the files to inputs on a new job: see reuse files across jobs.
My Library
Your own working space. Use it for:
- Meshes, geometry, and material data you'll reuse across many jobs.
- Reference files that aren't attached to anything.
- Organizing data the way you think about it, with folders you create.
Anything you upload as a job input also lands in My Library. That's deliberate: it means the file outlives the job. Delete the job later and the input is still in your library.
Two other things called "folders"
The word gets used three ways on the platform. They're unrelated:
Finding a specific file
The Files tab gives you a search box scoped to the space you're in, a date picker, and a Tags filter in the left rail. Tags are often the fastest route: see tags.
Search matches filenames, not paths, and deep search through nested folders is limited. If you know which job produced a file, going to that job's folder is faster than searching.
The legacy Files view has more filters
A separate legacy view still exists, reachable from the icon at the top right of the Files tab. It lists every file flat, with File ID, Latest Job, Type, Size, and Owner columns, and adds filters the folder view doesn't have:
Use it when you need to find a file by type across all jobs, or when you have a File ID and no idea which job it belongs to.
Why some filenames have a hash appended
If a file you upload would collide with one already at the same path, Rescale appends a short hash to keep them distinct: mesh.cas becomes something like mesh.cas-2oaTX_1yZ.
You'll see this most often on job inputs, because inputs are stored in a flat namespace. It isn't an error and the file content is untouched.
Storage usage per job
Both the jobs list and the My Jobs view show how much storage each job is consuming.
Since December 2025, a job's storage figure refreshes after you delete files rather than staying frozen at its completion-time value. The platform's own tooltip says usage "reflects output files and may take up to 30 minutes to update."
Two limits: it only refreshes when a deletion happens (nothing recalculates on a schedule) and jobs untouched since December 1, 2025 still show their original snapshot.
Files shared with you
When someone shares a job with you, you can view and download its files.
Shared files don't appear in your own file picker. To build on someone else's job:
- Open the shared job and download the files you need.
- Upload them into your My Library.
- Attach them as inputs to your new job.
Related
- Reuse files across jobs — attaching without duplicating
- The file lifecycle — trash, archival, deletion
- Upload files
- Share a job
- Organizations and workspaces — Workspace Folders