> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mudstack.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Pushing data

> Upload content to the cloud.

Pushing data involves uploading your local changes to the cloud. To view your local changes, click the `Changes` button in the top nav or the `View my changes` button located at the top right corner.

## Pushing Content to a Workspace

<Info>
  You **MUST** have have a local directory mapped to a cloud workspace to push
  local versions to the cloud. If your workspace is cloud only, [map the
  workspace](/features/sync-overview#mapping-a-workspace) first.
</Info>

Every modification you make to file metadata, libraries, tags, and workspace details will be included in the push table. This table displays only the pushes related to the currently selected workspace.

### Staging & Pushing Your Changes

On the Changes view, you will see a list of all local changes made by you. From here, you can select related changes in order to push them as a group with a push message title and optional description.

<Steps>
  <Step title="Select related changes">
    Choose the data you wish to push and stage it for a push by clicking the
    checkbox.
  </Step>

  <Step title="Describe your changes">
    Write a brief yet descriptive title to summarize the reason for your
    changes, with an optional more detailed description.
  </Step>

  <Step title="Upload your changes">
    Click the `Push Changes` button to send your changes to the cloud.
  </Step>
</Steps>

<Note>
  When you click the `Push Changes` button, Mudstack will
  [fetch](/features/syncing-data/fetch) before the push to check for
  [conflicts](/features/syncing-data/conflicts).
</Note>

By default, **only the current version** of any file in the staged area gets pushed to the cloud. In most instances, this will also be your last save for the file unless you manually set [an older local version to be the current version](/features/version-control#set-current-version).

### Unstaging Changes

At any point before clicking the `Push Changes` button, you can unstage changes to remove them from that push. To do this, simply uncheck the checkbox and that change will go back to the `Unstaged` area.

### Discarding Changes

You can discard a change by selecting one or more changes (either in the staged or unstaged section), right-clicking and selecting `Discard Changes` from the menu.

### Uploading Non-current Versions

If you want to upload any non-current local versions for any reason, Mudstack allows you to do this from outside of the regular push flow described on this page.

<Info>
  See [upload non current
  versions](/features/version-control#upload-non-current-versions) for more
  Info.
</Info>

## Automated Pushing

Some data will be pushed automatically. This will happen immediately after a change in order to maintain continuity with the cloud workspace.

Automated pushes include:

1. Account Data
2. Workspace Deletion
3. Workspace Creation -> Send to Cloud

## Cloud Import

On occasions where you need to import large volumes of content to Mudstack on a one-off basis, we recommend using our Cloud Import feature. This allows you to upload folders to the root of your workspace without going through the staging process.

This is much faster as it skips the local indexing and backing up process that is followed by the app when watching for changes and staging them for a push.

To use this feature, go to `Settings/Account/Workspaces`, select your workspace from the dropdown and then use the Cloud Import section to upload your content.