# Package types and naming

Source: https://www.jawsdeploy.net/rest-api/package-types

Supported package formats and the filename convention.

Jaws Deploy stores deployment artifacts as packages in workspace feeds. The [package upload endpoint](https://www.jawsdeploy.net/rest-api/package-store-upload) (`POST /api/packagestore/package`) accepts the following formats:

- .nupkg (NuGet)
- .zip
- .tar
- .tar.gz

## Filename convention

The uploader parses the package ID and version directly from the filename. Use:

```
<PackageId>.<Version>.<ext>
```

Examples:

```
Acme.Web.2.5.3.nupkg
Acme.Worker.2.5.3-rc1.zip
web-frontend.2026.05.16+sha.abcdef.tar.gz
```

The version segment must be a valid SemVer / NuGetVersion string. Filenames that don't parse get rejected with `400 Bad Request`.

See [Upload a package](https://www.jawsdeploy.net/rest-api/package-store-upload) for the request itself - the feed the package lands in, the multipart body, and the responses.