{"meta":{"title":"Workflow artifacts","intro":"Learn about storing and sharing data as artifacts of GitHub Actions workflows.","product":"GitHub Actions","breadcrumbs":[{"href":"/en/enterprise-server@3.21/actions","title":"GitHub Actions"},{"href":"/en/enterprise-server@3.21/actions/concepts","title":"Concepts"},{"href":"/en/enterprise-server@3.21/actions/concepts/workflows-and-actions","title":"Workflows and actions"},{"href":"/en/enterprise-server@3.21/actions/concepts/workflows-and-actions/workflow-artifacts","title":"Workflow artifacts"}],"documentType":"article"},"body":"# Workflow artifacts\n\nLearn about storing and sharing data as artifacts of GitHub Actions workflows.\n\n## About workflow artifacts\n\nAn artifact is a file or collection of files produced during a workflow run. Artifacts allow you to persist data after a job has completed, and share that data with another job in the same workflow. For example, you can use artifacts to save your build and test output after a workflow run has ended.\n\nGitHub provides two actions that you can use to upload and download build artifacts,  `upload-artifact` and `download-artifact` on GitHub Enterprise Server.\n\nCommon artifacts include:\n\n* Log files and core dumps\n* Test results, failures, and screenshots\n* Binary or compressed files\n* Stress test performance output and code coverage results\n\n## Artifacts versus dependency caching\n\nArtifacts and caching are similar because they provide the ability to store files on GitHub, but each feature offers different use cases and cannot be used interchangeably.\n\n* Use caching when you want to reuse files that don't change often between workflow runs, such as dependencies downloaded by a package management system, intermediate build outputs, or other files that are expensive to regenerate. Caching these files can speed up your workflow runs, though a job should always be able to re-download or regenerate these files if a cache isn't available.\n* Use artifacts when you want to save files produced by a job to use or view after a workflow run has ended, such as built binaries or build logs, or when you want to pass files between jobs in a workflow.\n\nFor more information on dependency caching, see [Dependency caching reference](/en/enterprise-server@3.21/actions/reference/workflows-and-actions/dependency-caching).\n\n## Artifacts from deleted workflow runs\n\nWhen a workflow run is deleted all artifacts associated with the run are also deleted from storage. You can delete a workflow run using the GitHub Actions UI, the REST API, or using the GitHub CLI, see: [Deleting a workflow run](/en/enterprise-server@3.21/actions/how-tos/manage-workflow-runs/delete-a-workflow-run), [Delete a workflow run](/en/enterprise-server@3.21/rest/actions/workflow-runs?apiVersion=2022-11-28#delete-a-workflow-run), or [gh run delete](https://cli.github.com/manual/gh_run_delete)."}