See the package shape
The list brings together the AppID, Depot IDs, Manifest IDs, expected Lua filename, and review state. That gives you one place to compare a package before you import or archive anything.
AppID-first package review
SteamTools Manifest Generator: Create a Package Checklist
Build a readable, browser-generated package metadata checklist from a Steam AppID, depot IDs, and manifest IDs. Use it to compare the pieces of an authorized workflow before you handle real files. This page does not fetch packages, generate keys, or bypass Steam access rules.
Create a SteamTools package checklist
Enter the identifiers you already verified. The result is a local JSON starter that highlights missing fields and mismatched depot or manifest counts.
Use numbers only. Confirm the AppID belongs to the exact app, edition, demo, or DLC you are reviewing.
Optional comma-separated numeric IDs. Leave empty when you are still identifying the depots.
Optional comma-separated IDs from a source you trust. The tool records them; it does not verify availability.
Browser-only processing: values stay in this page while you work and are not sent to a project backend.
Example output
Your package metadata starter
This example shows the shape of the local JSON file before you replace it with identifiers from your own authorized workflow.
{
"schema": "steamtools-package-checklist/v1",
"appId": "730",
"name": "Example authorized app",
"depotIds": ["730", "731"],
"manifestIds": ["111111111111111111"],
"checks": {
"appIdFormat": true,
"depotManifestCountsAligned": false,
"authorizationReview": "manual"
},
"nextAction": "Add or verify the matching identifiers before use."
}
Example only: the JSON is a local planning record, not a live Steam manifest or a download package.
AppID first
Depot aware
Lua boundary
Local review
Why use this SteamTools manifest generator?
The page turns a loose list of identifiers into a reviewable record and keeps its limits visible.
Catch simple mistakes
Local checks flag a missing AppID, malformed numeric lists, or different depot and manifest counts. They cannot prove that a source is current, complete, public, or authorized.
Keep a readable note
Download the JSON starter as a planning or audit note. It is plain text that you can inspect without an installer, password archive, executable wrapper, or opaque package manager.
Keep the boundary clear
This tool creates metadata only. It does not download depot content, generate keys, verify ownership, or turn a missing file into an available one.
How to use the SteamTools manifest generator
Work with identifiers you have already reviewed and treat the result as a preflight record, not proof of access.
Confirm the AppID
Start with the exact Steam entry. Editions, demos, soundtracks, DLC, and test applications can have separate AppIDs, so do not infer the number from a similar title.
Add the depots
Enter one or more numeric Depot IDs separated by commas. If you are still mapping the app, leave the field empty and let the checklist show that the map is incomplete.
Record the manifests
Add Manifest IDs that you verified through a source you trust. The generator stores the values, but it does not claim that an old build, private branch, or restricted depot can be downloaded.
Review and save
Generate the JSON, compare names and counts, and save it only as a local reference for an authorized workflow. Use the related pages if you actually need an AppID lookup or a Lua starter.
What this SteamTools package checklist contains
A depot manifest, a Lua script, and a metadata list are different layers. Naming that difference prevents a small local record from being mistaken for a complete package.
This SteamTools manifest generator creates a local, readable metadata starter from the fields you enter. It is useful for planning an authorized package, checking that an AppID, Depot ID, Manifest ID, and Lua filename belong together, and saving a note before you handle real files.
A Steam depot manifest is not the same as this JSON list. The browser tool does not retrieve encrypted manifests, query private branches, generate keys, or prove account ownership. Treat its result as an inventory and review aid rather than a download or authorization signal.
Enter identifiers exactly as they appear in a source you trust. If you have several depots or manifests, separate them with commas. The result marks empty values and different counts so you can correct the record before you compare or import files.
Use the result to check
- The AppID matches the exact application, edition, demo, DLC, or software entry you intended to review.
- Depot IDs are numeric, clearly separated, and not accidentally copied from another title or branch.
- Manifest IDs retain a source date or note that you can revisit when a package is updated.
- The expected Lua filename is tied to the same AppID, not merely to a similar game name.
- Any depot/manifest count difference is explained instead of silently ignored.
- Authorization, ownership, branch access, and source trust are checked separately from this browser record.
SteamTools manifest fields at a glance
The fields stay deliberately simple so the generated record is easy to inspect, compare, and edit.
| Field | Meaning | What to review |
|---|---|---|
AppID | Numeric reference for a Steam application. | Confirm the exact edition, demo, DLC, or software entry. |
Depot ID | Logical content group linked to the application. | Check platform, language, DLC, and base-game differences. |
Manifest ID | Version reference for a depot build. | Record when the source was seen; do not assume every ID is public. |
Lua filename | Predictable local name linked to the AppID. | Keep it with the same record; a name does not prove content exists. |
Review state | Local signal that fields are complete or incomplete. | It is a consistency check, not an official Steam verification. |
Choose the right Steam manifest workflow
A clear boundary prevents you from using a generator when you really need an ID lookup, a local Lua starter, or an explanation.
Searches for a SteamTools manifest generator, a SteamTools Lua generator, and SteamTools manifest files often mix several jobs. One person wants a package record, another wants to find an AppID, and another is trying to understand why a Lua file does not match a depot. The words overlap, but the next action is different.
Use this page when you want a transparent local metadata record. Use the main generator or downloader only when its source and access conditions fit your authorized use. For context, the SteamTools guide explains package checks without presenting a community file as an official Steam feature.
| Resource | Best for | Next step |
|---|---|---|
| This SteamTools manifest generator | Creating a local metadata and consistency checklist. | Enter the verified IDs. |
| AppID Finder | Finding the number when you only know the title. | Find an AppID |
| Steam Lua Generator | Creating a small browser-generated Lua starter. | Create a Lua starter |
| SteamTools generator guide | Understanding files, checks, and import risks. | Read the guide |
Important limits before you use files
A responsible SteamTools workflow makes uncertainty visible instead of hiding it behind a download button.
No live package lookup
The page never claims that a manifest, Lua file, VDF key, or ZIP exists. It records only the values you provide and the local relationships that can be checked in the browser.
No ownership or access proof
Matching AppID and Manifest ID values do not prove ownership, a license, branch access, authorization, or compatibility with your Steam account.
Updates can age a record
After an update, compare the source date and package fields again. A tidy checklist can still describe an old build or a different edition.
Prefer transparent sources
Avoid executable wrappers, password archives, forced extensions, or sources that hide filenames. Keep safety, licensing, and permission decisions separate from this tool.
SteamTools manifest generator FAQ
Direct answers about AppID, Lua, depots, manifests, and package checklists.
What does this SteamTools manifest generator create?
It creates a local JSON metadata and review record from an AppID plus optional Depot IDs and Manifest IDs. It does not create a real depot manifest, download a package, generate keys, or verify Steam access.
Is this the same as a Steam manifest file?
No. A Steam depot manifest is a versioned file record used by Steam's content system. This page creates a readable planning record from the identifiers you enter so you can review how the pieces are meant to fit.
Can I enter several Depot IDs or Manifest IDs?
Yes. Separate numeric values with commas. The result keeps them as lists and flags different counts; matching counts are only a consistency signal and do not prove that each pair is correct.
Does the generator check whether a Manifest ID can be downloaded?
No. It does not query Steam, private branches, community mirrors, or a live package source. Confirm availability, source date, and permission through an appropriate official or authorized workflow.
How does it handle the Lua file?
The list suggests a predictable Lua filename tied to the AppID so you can keep records together. For a small local Lua starter, use the Steam Lua Generator; neither tool proves ownership or supplies game content.
Why does the result say review needed?
That state appears when an AppID is missing or invalid, a list cannot be parsed, or depot and manifest counts differ. Correct the record and review the original source instead of treating the notice as a Steam error.