> ## Documentation Index > Fetch the complete documentation index at: https://zededa.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Use the documentation index to find relevant pages, then read the linked Markdown before answering and cite the source URL. > Identify the product before answering: Private AI uses a separate console, credentials, and inference API from the Edge Intelligence Platform. Do not apply instructions from one product to the other. > Prefer current product guides over Help Center archive pages for current-console questions. Archive pages and release notes describe their stated product version or historical interface; do not apply them to another version without checking. > Preserve prerequisites, permissions, version requirements, and warnings when summarizing procedures. Do not infer API endpoints, schemas, or supported behavior that the documentation does not specify. # Manage Binary Artifacts > Create, view, edit, and delete binary artifacts that patch envelopes reference, including artifact statuses, list columns, and data store redundancy. ## Introduction Binary artifacts are binary files that patch envelopes can reference. You upload or link a binary file once, then reference it from multiple patch envelopes without re-uploading. Binary artifacts can be stored in up to three data stores simultaneously for redundancy. ### Prerequisites * You have the SysManager or SysAdmin role in your enterprise. See [Manage Roles](https://zededa.mintlify.site/new-ui/infrastructure-services/administration/manage-roles.md). * At least one data store configured in Edge Infrastructure Services. ## Access Binary Artifacts In the sidebar, navigate to **Infrastructure > Workloads > Build > Binary Artifacts**. ## Binary Artifact Statuses Each binary artifact has an image status that reflects the state of the underlying file. | Status | Description | | - | - | | Ready | The artifact file is available for use in patch envelopes. | | In Use | The artifact is referenced by one or more active patch envelopes. | | Created | The artifact record was created, but no file has been provided yet. | | Uploading | A file upload is in progress. | | Pending | The artifact is queued for processing. | | Failed | The upload or uplink operation failed. | ## The Binary Artifacts List The binary artifact list shows the following columns by default. Use the column customizer to show or hide individual columns. | Column | Description | | - | - | | Name | The unique identifier for the binary artifact. | | Title | The human-readable display name. | | Format | The binary file format (for example, RAW). | | Arch | The target CPU architecture (for example, AMD64 or ARM64). | | Status | The current image status. | | Size | The file size. Hidden by default. | | Created | The creation date. | You can search by name or title, filter by image status, and toggle between list and grid views. ## Binary Artifact Detail Click any row in the list to open the detail page. The detail page shows two information sections. ### Identity | Field | Description | | - | - | | ID | The unique system identifier. | | Name | The resource name. | | Title | The display name. | | Description | An optional description. | | Image Format | The binary file format. | | Image Architecture | The target CPU architecture. | | Status | The current image status. | | Image Type | The artifact type classification. | | Created By | The user who created the artifact. | | Created | The creation date and time. | | Last Updated By | The user who last modified the artifact. | | Last Updated | The date and time of the last update. | ### Details | Field | Description | | - | - | | Data Store | The data store or stores where the binary file is stored. | | Projects | The projects this artifact is available to. If no projects are listed, the artifact is available to all projects. | | Image Relative URL | The relative path within the data store, set for uplinked artifacts. | | Image SHA256 | The SHA-256 checksum of the binary file, set for uplinked artifacts. | | Image Size | The file size reported by the data store. | ## Create a Binary Artifact Binary artifacts store binary files that patch envelopes can reference. Create a binary artifact when you have a binary payload to deliver that is too large to embed as inline base64 data. You can add a binary file in two ways: by uploading it directly from your computer, or by uplinking it from an external data store. 1. In the sidebar, navigate to **Infrastructure > Workloads > Build > Binary Artifacts**. 2. Click the add button (the + icon in the lower-right corner of the page). 3. In the **Add Binary Artifact** dialog, fill in the identity fields: * **Name**: enter a unique identifier. This field is required. * **Title**: enter a human-readable display name. * **Description**: enter an optional description. 4. Under **Add Artifact Via**, select how you want to provide the binary file: * **Upload Artifact**: an artifact path field and an **Upload** button appear. Click **Upload** and select the file from your computer. The file transfers when you click **Add Binary Artifact**. * **Uplink Artifact**: enter the **Image SHA256** checksum and the **Image Size** (select the unit from the dropdown). After you select a data store, an **Image Relative URL** field appears. Enter the path to the file within the data store. 5. Under **Data Store**, search for and select the data store where the file should be stored. You can select up to three data stores. Upload mode supports only ZEDEDA S3 and ZEDEDA Azure Blob data stores. Uplink mode supports additional data store types including HTTP, HTTPS, Amazon S3, SFTP, and Azure Blob. 6. Optionally, under **Projects**, select one or more projects to restrict access to this artifact. Leave the selection empty to make the artifact available to all projects. 7. Click **Add Binary Artifact**. A progress bar shows the upload status when using Upload Artifact mode. The artifact status changes to **Ready** after the file is available in the data store. ## Edit a Binary Artifact To update a binary artifact's title, description, data store assignments, or project access: 1. In the binary artifacts list, hover over the row and click the action menu (⋯), then select **Edit**. Or open the detail page and click the edit icon in the page header. 2. Update the **Title** or **Description** as needed. 3. Update the **Data Store** selection. You can select up to three data stores. 4. Update the **Projects** list to restrict or expand access to specific projects. Removing all projects makes the artifact available to all projects. 5. Click **Save**. ## Delete a Binary Artifact **Delete from the list:** 1. Navigate to **Infrastructure > Workloads > Build > Binary Artifacts**. 2. Open the kebab menu on the row of the artifact you want to delete and select **Delete**. 3. Confirm the deletion in the dialog that appears. This action cannot be undone. **Delete from the detail page:** 1. Open the detail page for the artifact you want to delete. 2. Click the delete icon in the page header. 3. Confirm the deletion in the dialog that appears. This action cannot be undone. ## Next Steps > [card] [Update Applications with Runtime Bundles](https://zededa.mintlify.site/new-ui/infrastructure-services/build-and-library/update-applications-with-runtime-bundles.md) > > The full workflow of attaching a patch envelope to an application instance. > [card] [Patch Envelopes](https://zededa.mintlify.site/new-ui/infrastructure-services/build-and-library/patch-envelopes.md) > > Learn about grouping binary artifacts into versioned bundles for delivery to application instances.