Before you ZIP an asset pack: six checks worth making
A useful handoff answers three questions: what is in this folder, what does the recipient need, and what are they allowed to do with it? This checklist works with an ordinary file manager and a text editor. 日本語はこちら
1. Write down what must be present
A tool cannot know whether a missing file was intentional. Start with exact relative paths agreed with your recipient. Use one path per line; do not add the selected folder’s own name.
textures/grass.png textures/stone.png README.txt LICENSE.txt
This verifies presence only. It does not inspect the materials a 3D scene references or whether a game can load them.
2. Look for names that collide
Two paths that differ only by letter case or Unicode composition may be distinct in one environment and difficult to distinguish in another. Review pairs such as Hero.png and hero.png. Keep the names your project expects. A tidier name is not helpful if it breaks an internal reference.
3. Compare content, not only names
grass.png and grass-copy.png might contain the same bytes. A content hash is useful for finding candidates. Identical content does not mean one is safe to delete: your project may reference both paths. Decide in the source project.
4. Include a visual index when it helps
A contact sheet helps a recipient browse raster images. Numbered labels and a path map are useful when names are long. Non-image assets still belong in the inventory. A missing thumbnail must not be mistaken for a missing file.
5. Keep permissions attached
Add the actual permission or licence you have for each included asset. Do not infer permission from a filename or the fact that an asset was free. Resolve any uncertainty about redistribution before including a file.
6. Open the ZIP as the recipient would
Extract into a fresh folder. Read the README, compare the inventory with the files, and test the result in the intended application. A hash list can help confirm bytes, but cannot certify that a project works.
Project: Version: Prepared by: Contents: How to use: Known limitations: Asset permissions: Contact / support:
When is a dedicated tool useful?
| Situation | A reasonable starting point |
|---|---|
| A handful of files, one handoff | File manager + README |
| Repeated handoffs with required paths | Saved checklist + duplicate report |
| Many raster previews and an inventory | Contact sheet + packaging tool |
Our demos combine these steps into a local browser workflow. They do not replace your engine, editor or judgement. Try Asset Check or try Delivery Pack with the synthetic sample first.
素材をZIPにする前に確認したい6項目
受け取る人が知りたいのは「何が入っているか」「どう使うか」「どこまで使ってよいか」です。ファイル管理ソフトとテキストエディタだけでも、次の確認ができます。
- 必須パスを決める。 受け手と合意したファイルを、選択フォルダからの相対パスで1行ずつ列挙します。指定されていない不足は推測できません。
- 名前の衝突を確認する。 大文字小文字やUnicode表記だけが違う名前を確認します。参照のある素材を改名すると、プロジェクトが壊れる場合があります。
- 内容の重複を確認する。 ハッシュで同じ内容を探します。同じ内容でも両方のパスが使われている可能性があります。
- 必要なら画像一覧を添える。 長い名前には番号と対応表を使います。プレビューのない素材も素材表から漏らさないようにします。
- 実際の利用条件を添える。 無料だったことや名前だけで再配布の許可を判断せず、利用範囲を確認します。
- 受け手として展開する。 新しいフォルダにZIPを展開し、説明書と素材表を照合。使用するアプリでも確認します。
少数の素材なら手作業で十分です。繰り返す納品で手間になる場合に、無料見本の Asset Check と Delivery Pack を試してください。どちらもエンジンの動作や権利の有無を保証するツールではありません。
Original workflow note. Examples are synthetic. Written with AI assistance and reviewed against the tool’s documented scope.