> For the complete documentation index, see [llms.txt](https://docs.sealsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealsecurity.io/discovering/importing-manifests/snyk-export.md).

# Importing from a Snyk export

Importing a Snyk CSV gives Seal a one-time view of the vulnerable packages a Snyk environment has identified. The Seal Project lands in [imported manifest discovery mode](/discovering/package-discovery-mode/imported-manifest.md). The snapshot does not refresh.

This is the path for bringing Snyk-discovered vulnerabilities into Seal. The separate [Snyk integration](/integrations/internal-scanners/snyk.md) goes the other direction (it lets Seal inform Snyk about the vulnerabilities it has remediated) and does not import findings from Snyk into Seal.

## Generating the export from Snyk

In the Snyk UI, export the project's findings as CSV. The format Seal expects matches Snyk's standard project-level CSV export.

## Steps

Follow the [shared Import from file flow](/discovering/importing-manifests.md#the-shared-flow). Drag the `.csv` onto the upload area; the detector identifies it by extension and contents.

## Verify

The new Seal Project appears on the Projects page in **Imported manifest** discovery mode. Discovered packages appear on the Protection page's Vulnerable packages tab as the parser finishes.

## Related

* [Importing manifests & SBOMs](/discovering/importing-manifests.md): the parent overview.
* [Snyk integration](/integrations/internal-scanners/snyk.md): the live, refreshing alternative to a CSV upload.
* [Imported manifest mode](/discovering/package-discovery-mode/imported-manifest.md): coverage and refresh behavior.