Novus Convert
Convert files
Archive format

NUPKG converter

A .nupkg file is the package format for the .NET ecosystem. It is an Open Packaging Conventions ZIP holding a .nuspec manifest, assemblies arranged under lib/ by target framework, and optional build props, content files, and tools that consuming projects pick up automatically.

Private for supported formats — processed in your browser

Convert supported files

Runs on your device

Drop NUPKG files here

Batch files can each use a different output. Nothing uploads for local conversions.

Working inputs include camera RAW, browser-local audio/video, PDF, CBZ/CBR comics, office documents, ebooks, markup, 3D models, structured text, images, and archives.

Where NUPKG comes from

NuGet launched in 2010 as NuPack, built on the same Open Packaging Conventions Microsoft had already used for Office documents. The PackageReference model in 2016 moved dependency declarations into project files, and .NET Core's dotnet pack made producing packages part of the SDK rather than a separate tool.

How NUPKG works

  • The container follows Open Packaging Conventions, so it carries a [Content_Types].xml alongside the payload.
  • The .nuspec manifest declares the package id, version, authors, licence, and dependency groups per target framework.
  • Assemblies live under lib/<tfm>/, and restore selects the closest compatible target framework moniker.
  • build/ and buildTransitive/ folders can inject MSBuild props and targets into any project that references the package.
  • Symbol packages use the .snupkg extension and carry portable PDBs separately from the main package.

When to use NUPKG

  • Reading a package's manifest to check its licence and dependency graph before adoption.
  • Extracting a single assembly from a package for offline analysis.
  • Verifying which target frameworks a library actually ships binaries for.
  • Converting a package into a plain archive for a build system without NuGet support.

Strengths and limitations

Strengths

  • Framework targeting is explicit in the folder layout rather than guessed at restore time.
  • The manifest travels inside the package, so metadata never depends on a feed being reachable.
  • A standard ZIP container, readable with ordinary tools on any platform.
  • Build customisation ships with the package instead of requiring separate instructions.

Limitations

  • Target-framework fallback rules are subtle and can produce surprising assembly selection.
  • Packages that inject MSBuild targets can change a build in ways that are hard to trace.
  • Native dependencies still have to be handled outside the managed lib/ layout.

Compatibility

The dotnet CLI, NuGet.exe, Visual Studio, and JetBrains Rider all consume the format on Windows, macOS, and Linux, and any ZIP utility opens one. Novus Convert unpacks the ZIP locally and republishes the members as ZIP or TAR; no MSBuild targets from the package are evaluated.

Package id, version, authors, licence expression, repository URL, and dependency groups live in the .nuspec file, which extraction preserves verbatim along with the Open Packaging Conventions content-type map.

Convert NUPKG to another format