# Files and results > Inspect current and earlier node outputs, copy useful results to Files, organize personal and team assets, and download copies for use elsewhere. Source: https://kaitoi.io/docs/studio/files-and-results/ Section: Kaitoi Studio / Projects, files and teams Written for: Anyone working with generated media or uploaded files. Last reviewed: 2026-10-24 --- A node's current output, its earlier run snapshots, an item in **Files**, and a download on your computer serve different purposes. Keep the editable project when you need the workflow; keep a separate file when you need the deliverable. ## Choose where to keep a result The example starts with a coral-kite image already produced by a node. **Inspect in project** shows that result in the project; it creates no Files item or download. **Copy to Files** assumes a successful copy of the stored image into the top folder of Personal Files. The node's result stays in place. **Download a file** assumes a successful image download to your computer; that does not create a Files item. Neither copy action saves the editable project. These independent examples use authored artwork, not actual outputs. The controls do not run a node, copy a file, or start a download. *Figure: Compare inspecting a node result, copying a stored image into Personal Files, and downloading an image to your computer.* ## Inspect a result Use the node preview to inspect an output. When a node has several outputs, check which output is displayed before copying or downloading. A thumbnail may be a smaller image or a poster frame; inspect the original when quality, resolution, or playback matters. Open the node's **History** for earlier snapshots. Selecting one restores its recorded inputs and outputs into the node and updates its cached result. This changes working graph state; it is more than opening an older picture. Review the selected version and inputs before continuing or running downstream work. See [Runs](/docs/concepts/runs/) for cached results and changed inputs. ## Browse outputs across the graph Open **Browser → Outputs** to browse supported results from node history in the current graph. Use search, media-type filters, and the **Active**, **Current**, and **History** filters to narrow the list. Current matches the node's current output value; Active also matches its active preview output; History shows other values. These filters describe node state, not whether a file has been copied to Files. Use **Refresh** to recollect results after the graph changes while the browser is open. Clear an album, search, or filter that may be hiding an item before assuming it is lost. The browser is a view of available project history, not a complete account-wide archive. An output with no retained history entry may not appear here. Selecting results with **Preview** enabled changes the node state used for previewing. The close action tries to restore the version and active output selected when it opened. Check the node's version, inputs, and displayed output before continuing, especially after removing history. Directly selecting a snapshot in the node's own History is a separate action. ## Send graph results to Personal Files Right-click a graph node and find the **Send to Files** section. If the clicked node belongs to the selection, the menu can act on the selected nodes. The displayed count helps you check the scope: - **Send active output** takes one eligible output per target node. It prefers the displayed output; if that cannot be sent, it uses the first eligible one. - **Send all outputs** takes all eligible outputs in those nodes' current result state. It does not export every historical run. Stored file outputs are copied, and nonempty text outputs become **Markdown files**. Numbers, booleans, colors, empty results, and a URL that merely points elsewhere do not become stored media through this action. If there is nothing eligible, the menu explains that instead of offering a copy. ## Check the send destination and result This action writes to the **top folder of Personal Files**, including when the graph belongs to a team. It does not follow the Files workspace picker. Each send creates new copies. Wait for the completion notice: a partial result can mean some files saved and others failed, so inspect Files before repeating the whole action and creating duplicates. ## Copy a historical file In **Browser → Outputs**, open a result tile's menu and choose **Copy to Files** (the label includes a count for a selection). For a stored file, this copies the chosen historical output into Personal Files. Read the success or partial-copy notice before proceeding. For inline text, use the graph's **Send to Files** flow to create Markdown. The Outputs browser's copy action copies stored filenames; it does not perform that text conversion. A displayed URL or thumbnail is not proof that a source file is available to copy. ## Organize and reuse assets Open **Browser → Files**. Use **Upload** to add files or a folder, or drop files into the library. Choose **New Folder** to organize them. Search matches file names and types in the current folder; navigate into another folder when needed. Watch upload progress and any partial-failure notice rather than assuming every selected file arrived. Double-click a file, or use **Add to Graph**, to create a loader node. Studio copies the library file into your working storage, then runs that loader; the original library item remains. This can use additional storage. Check the new node for a load failure before running the rest of the graph. ## Choose Personal or team Files The Files workspace picker shows **Personal** or a team name. It appears when team choices are available. This selects whose library you are browsing; it does not change who owns the current project. Check it before uploading, organizing, or transferring files. Team members can browse and read their team's Files. Owners, admins, and editors can add, change, and remove team items. A viewer can copy readable team files to Personal Files, but cannot move them out or write into the team library. See [Teams](/docs/studio/teams/) for ownership and roles. ## Copy or move between workspaces Select files or folders and use the available **Move or Copy to...** action (**Copy to...** for a read-only team library). Choose the destination workspace, folder, and operation. From Personal Files you can transfer to a team you can write to; from a team's Files you can transfer to Personal Files. Both examples start with one coral-kite file in Personal Files and no copy in the example team's Files. **Copy to team** keeps the Personal file and creates a separate team-owned item. **Move to team** creates the team item and removes the Personal source after the destination is created. Both actions require permission to write to the team. These are independent successful examples, not a sequence; they do not transfer a real file or change permissions. *Figure: Compare a successful copy to a team with a successful move to that team.* ## Keep references working Choose **Copy** when existing work still needs the source. Moving Personal files into a team can break timeline clips that refer to their old library locations; Studio checks the current timeline and warns when it finds those references. Do not treat that check as a scan of every project. A batch can partly succeed. Review the reported result and both libraries before retrying. If an item changes during a move, both copies may be kept rather than removing the changed source. ## Albums and deletion In Outputs, **Add to Album** groups references to results for browsing. **Remove from Album** removes that membership. It does not make a separate media copy. A project collection organizes projects instead; neither feature replaces saved projects or external copies of deliverables. Read deletion prompts carefully. Deleting an output tile removes its whole history snapshot, which can include other outputs from that run. Deleting a Files item removes the library file; deleting a folder includes its contents. Files deletion cannot be undone through a library trash. Preserve needed assets first, especially files used by a timeline. ## Downloads and links Use an output tile's **Download** action for an individual stored file, or the Files library's download controls for selected assets. Confirm that the file arrived and opens on your computer. Downloading media does not save the graph, copy an item into Files, or preserve its inputs and connections. A preview URL may be temporary or signed. Use the file's download action to obtain a fresh link instead of keeping the displayed URL as a permanent public address. For programmatic access, use the existing [REST API guide](/docs/core/runs-and-files/). ## If media will not load Check the connection, selected workspace, folder, search, and filters first. Refresh Outputs or reopen the file view to try obtaining fresh links. Confirm the source still exists and that you can access it. A cached thumbnail can remain after a full-size file becomes unavailable. Project backups preserve project snapshots; they are not a guarantee that every referenced external file or service remains available. Keep important deliverables in your own storage as well. See [Saving and recovery](/docs/studio/saving-and-recovery/) for recovering the editable project.