Keep your Unity assets and plans to use them in your projects organized.

Getting Started

GAIN - Game Asset Index tracks the Unity Asset Store packages you own, the Unity projects that use them, and the specific prefabs, textures, audio files, and animation clips found in those projects.

Demo mode is read-only. Sign in with your email before importing assets or scanning projects. The app sends a magic link and saves library data to your account after sign-in.

1. Import your owned Unity Asset Store assets with Import asset tool.
2. Add your Unity projects on Projects page.
3. Scan your Unity project root folder to find installed packages, prefabs, textures, audio files, and animation clips.
4. Review scanner suggestions, then link packages from Projects or individual files from their library pages as 'Planned' or 'Used in'.

Account and Limits

The account menu lives at the bottom of the left sidebar. It shows the signed-in account or Demo mode, the current plan, and account actions. Feature limits come from the active subscription tier.

Canceling or losing Pro access does not delete assets, projects, usage records, project links, scanned file metadata, saved searches, or other library data. If your account has more data than the Free plan includes, the full library stays visible and the Free limits apply to new additions.

1. Open the profile summary at the bottom of the left sidebar.
2. Use Account settings to view email, plan, and user ID.
3. Use Subscription to check tier, subscription state, asset package capacity, asset file capacity, project capacity, renewal date, checkout options, and billing portal access.
4. Free access includes 30 asset packages, 10,000 asset files, and 2 projects.
5. If your library is over the current limit, delete records to get back under the limit or restore Pro before adding or importing more asset packages, asset files, or projects.
6. Existing records can still be reviewed, edited, linked, unlinked, or deleted while the account is over the Free limits.
7. CSV export is a Pro feature and is unavailable while the account has Free access.
8. Use Logout from the account menu when you need to sign out.
9. Large imports and scans fail visibly when adding the new rows would exceed the current asset package or asset file limit.

Import Assets

Open Import asset in the left sidebar to add Unity assets one at a time, scan local .unitypackage files, bulk import owned Unity Asset Store assets, import CSV records, or export the current library to CSV.

The actual asset files you import or scan are not uploaded to the GAIN - Game Asset Index server. GAIN - Game Asset Index stores library metadata for your account, while project source files and .unitypackage contents stay on your computer and previews are generated locally in your browser.

1. Use Import URL for a Unity Asset Store product page. GAIN - Game Asset Index reads the public store page and fills the asset name, source URL, package ID when available, license, tags, art style, engine compatibility, and notes.
2. Use Upload .unitypackage to parse a local Unity package file, create an asset package record, scan package contents, store a private local package link in this browser when supported, and generate local previews without creating project usage.
3. Use Copy script in Unity owned assets to copy the browser exporter script, then upload the downloaded gain-unity-owned-assets.json with Upload owned assets JSON.
4. Use Import CSV for spreadsheet imports. The CSV must include name, sourceType, and sourceUrl. sourceType must be unity_asset_store and sourceUrl must point to assetstore.unity.com.
5. Use Export CSV to download a backup with name, source type, URL, package ID, license, tags, art style, compatible engines, purchase date, source notes, and notes.

Import Owned Unity Store Assets

Unity does not provide a simple public CSV export for every asset you own, so GAIN - Game Asset Index includes a browser script that runs against your signed-in Unity Asset Store My Assets page.

1. In GAIN - Game Asset Index, open Import asset, then use Copy script in the Unity owned assets section.
2. Open assetstore.unity.com in the same browser, sign in to Unity, and go to My Assets.
3. Open browser developer tools: press F12, or right-click the page and choose Inspect.
4. Switch to the Console tab. If the browser shows a safety warning before paste is allowed, type the exact confirmation text it asks for, such as allow pasting, and press Enter.
5. Paste the copied script into the Console prompt and press Enter to run it.
6. Wait for the browser to download gain-unity-owned-assets.json. Do not close the Unity Asset Store tab until the download starts.
7. The script calls Unity's My Assets endpoint with your current Unity session, downloads gain-unity-owned-assets.json, which includes all your owned assets.
8. Return to GAIN - Game Asset Index and upload gain-unity-owned-assets.json with Upload owned assets JSON.
9. GAIN - Game Asset Index skips duplicates by source URL, package ID, and Unity Asset Store ID.

The script needs your active Unity Asset Store session and the Unity CSRF cookie, so run it from My Assets while signed in to the Unity Asset Store.

Asset Packages

Asset Packages is the main ownership table. Each package can store license notes, tags, art style, compatible engines, purchase date, source notes, personal notes, and an optional local-only package path note on the current device.

1. Filter by asset name, tag, engine, art style, source, project status, or project.
2. Sort by asset name, tags, engine support, linked projects, purchase date, import date, or source.
3. Select visible rows when you need to bulk link assets to a project as planned or used.
4. Open a package row to review ownership metadata, usage evidence, project links, imported notes, and personal notes.
5. Use the row actions menu to edit a package, copy the source URL, copy a saved local package path, or remove the package from the index.

Search and Saved Searches

The top search box searches across Asset Packages, Prefabs, Textures, Audio, and Animations. GAIN - Game Asset Index can move you to the best matching library view when a query has results elsewhere.

1. Type in what you want to find.
2. Use 'and' or 'or' between terms, such as 'shader and water' or 'icons or ui'.
3. Use quotes for exact phrases, such as "sword and shield".
4. Use the help icon beside the search box to review search operator examples.
5. Use the bookmark icon beside the search box to save the current query, load a saved query, or delete a saved query.

Invalid searches show an error in the top bar. Close quotes and add a term after and or or before saving a search.

Projects and Plans

Projects track where package assets are planned to be used or actually used. Scanned prefab, texture, audio, and animation file links are managed from their own library pages.

1. Create a project with a name, optional Unity version, and optional notes.
2. Expand or collapse each project from the project header.
3. Use Link package to add an owned asset to the project as Planned or Used in.
4. Use Prefabs, Textures, Audio, and Animations to connect individual scanned files to projects.
5. Use 'Planned' and 'Used in' controls to change package link states as the project changes.
6. Use Unlink when a package asset should no longer be associated with the project. If that package link came from an accepted scanner suggestion, the suggestion returns to review.
7. Use Accept all visible or Reject all visible when scanner suggestions are ready to handle in bulk.

Unity Project Scanner Requirements

The scanner runs in your browser and reads a local Unity project folder that you choose. Source files stay on your machine.

1. Use a Chromium-based browser with File System Access API support, such as Chrome or Edge.
2. Navigate to the Import asset page. If the File System Access in not enabled, you will see instructions how to enable it.
3. Allow the browser's folder permission prompt. The scanner needs read access to the selected folder.
4. Select the Unity project root folder. Do not select the Assets folder or the Packages folder directly.
5. The selected root must contain Packages/manifest.json and Assets/ folder.
6. Keep Library/PackageCache available when possible. GAIN - Game Asset Index uses it to read package.json display names for installed packages.

If the Scan Unity folder button is disabled, the current browser does not expose the File System Access API to GAIN - Game Asset Index.

Scan Unity Package Files

A .unitypackage import reads the package archive in the browser, creates one asset package, and adds supported package contents to the file libraries. It does not create project usage because the package is not installed in a Unity project.

1. Open Import asset, then upload a .unitypackage file from the Unity package file section.
2. The import uses a deterministic local package ID and source URL based on the package SHA-256 hash, so importing the same file twice fails visibly as a duplicate.
3. Prefabs, textures, audio files, models, and animation clips inside the package are saved as package-origin asset files without a project.
4. Package-origin prefabs, textures, audio files, and animation clips can be manually linked to a project as Planned or Used in.
5. Preview generation uses package preview images when available, or extracted package bytes for supported texture, audio, prefab, and animation previews.
6. If local source links are reset or browser site data is cleared, re-import the .unitypackage to restore local access.
7. Use Edit asset to enter a local package path note when you want GAIN to show and copy the package location later. This path note is stored only in this browser and does not grant automatic file access.

Scan Unity Projects

Open Projects, select or create the project you want to update, then run Scan Unity folder. The scanner reads package dependencies, asset folders, project files, Unity .meta GUIDs, and supported local preview sources.

1. Package scanning reads Packages/manifest.json and ignores Unity-authored package IDs that start with com.unity.
2. Folder scanning checks top-level and second-level folders under Assets, while ignoring common organization folders such as Editor, Gizmos, Plugins, Resources, Scenes, Settings, Streaming Assets, TextMesh Pro, Images, and Scripts.
3. File scanning walks Assets/ and tracks prefabs, textures, audio files, models, and animation clips even when no matching asset package exists yet.
4. Package metadata enrichment reads Packages/<package>/package.json or Library/PackageCache/<package>@*/package.json when present.
5. Project scanning records AnimatorController-to-prefab relationships locally so animation previews can use targeted source files instead of scanning the whole project later.
6. Usage matches with exact package IDs or exact source URLs are linked automatically as used.
7. Name, token, and publisher/folder matches become scanner suggestions for review.
8. Accept a suggestion to save it as scanner usage evidence and link the asset to the project. Reject suggestions that are wrong.
9. Use Stop scan while a scan is running if you need to cancel it.
10. While scanning, you can navigate within the application, but refreshing the page also cancels the scan.

Prefab, Texture, Audio, and Animation Libraries

After a scan or .unitypackage import, GAIN - Game Asset Index lists local files in the Prefabs, Textures, Audio, and Animations views under Asset Packages in the left sidebar. Project-scanned files appear even before they match an asset package; package metadata appears when a match exists.

1. Prefabs shows scanned .prefab files and a preview image of each one.
2. Textures shows .png, .jpg, .jpeg, .tga, and .psd files and a preview image of each one.
3. Audio shows .wav, .mp3, .ogg, and .aiff files and a amplitude waveform preview of each one.
4. Animations shows .anim clips and embedded .fbx, .glb, and .gltf clips. .anim clips open a 3D playback view when paired to a prefab through AnimatorController references or prefab target guessing; embedded model clips play on their source model.
5. Models are scanned for matching and prefab preview support, but the app does not show a separate model library.
6. Filter by file name or path, tracked asset or no package, linked project, usage status, and preview status where available.
7. Select project-scanned or package-origin files to bulk link them to a project as Planned or Used in.
8. Open prefab 3D views from supported prefab preview cards. Open animation 3D playback from supported animation preview cards. Open texture previews full screen from the texture preview button. Play audio files from waveform or audio controls when source access is available.

Local Previews and Cache

Local previews and local source links are generated in the browser from files inside the selected Unity project folder during scanning, or from extracted .unitypackage bytes during package import. GAIN - Game Asset Index stores preview images, waveforms, project folder handles, package file handles, source file handles, and manually entered package path notes in browser IndexedDB.

1. Prefab previews need the prefab to reference a local .glb, .gltf, .obj, or .fbx model through Unity .meta GUIDs.
2. Prefab 3D view uses the same supported model references as prefab previews and needs local source access from the scanned Unity folder or imported .unitypackage.
3. Animation previews need either a supported .anim transform clip plus a targeted prefab, or a .fbx, .glb, or .gltf model with embedded animation clips listed in its Unity .meta file. For .anim clips, GAIN tries AnimatorController links and prefab target guessing automatically; when neither finds the right prefab, choose one from the animation 3D view and search by prefab name or path.
4. Texture previews support PNG, JPEG, and TGA images. PSD files are tracked but do not generate image previews.
5. Audio previews need Web Audio API support and show waveform data for supported audio files.
6. Projects shows Local Preview Cache size, preview count, and stored source link count.
7. Use Clear previews in Projects when previews are stale.
8. Use Reset source links in Projects when stored project folders, packages, or source file links need a reset.
9. If a project source file cannot be opened later, rescan the project folder to restore browser file access. If package-origin previews are missing after resetting source links or clearing browser site data, re-import the .unitypackage.

Local preview data, local source links, and manually entered package path notes stay in the browser on the current device. Browser privacy rules do not expose full operating-system paths to the web app, so GAIN shows selected file or folder names, Unity/package-relative paths, and any path notes you entered yourself. Clearing browser site data removes cached previews, stored file handles, and local path notes. If you use this application on multiple computers, you need to scan the project folders, re-import .unitypackage files, or re-enter local path notes on each one.

Troubleshooting

Here are some common errors you might encounter. If you have problem, you cannot resolve, feel free to contact support at admin@gameassetindex.com.

1. Unity owned assets import says CSRF token not found: sign in to Unity Asset Store and run the script from My Assets.
2. Owned assets JSON import fails: confirm the file is valid JSON downloaded by the GAIN - Game Asset Index script.
3. .unitypackage import fails as duplicate: the same package file hash is already in your library.
4. Scan fails while reading package manifest: select the Unity project root folder that contains Packages/manifest.json.
5. Scan button is unavailable: make sure you are using Chrome or Edge.
6. No files appear after scanning: confirm the selected Unity project has supported files under Assets/ and scan the project root again.
7. Preview generation fails: check the supported preview formats and whether Unity .meta files are present.
8. Original source file unavailable: rescan the project folder or re-import the .unitypackage.