---
name: build-with-arcgis-maps-sdk-for-unity
license: Apache-2.0
description: "Use this skill to build Unity apps with ArcGIS Maps SDK for Unity. Choose Map Creator, Components, or the C# API; add supported ArcGIS data; follow current setup, authentication, and compatibility guidance; and validate scenes and deployment targets. Consult the linked API reference for C# details."
title: build-with-arcgis-maps-sdk-for-unity
canonical_url: https://skilld.dev/gh/esri/esri-developer-agent-skills/build-with-arcgis-maps-sdk-for-unity
last_updated: 2026-11-17T00:30:23.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install esri/esri-developer-agent-skills/build-with-arcgis-maps-sdk-for-unity`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/build-with-arcgis-maps-sdk-for-unity`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/esri/esri-developer-agent-skills/build-with-arcgis-maps-sdk-for-unity) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/build-with-arcgis-maps-sdk-for-unity`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/build-with-arcgis-maps-sdk-for-unity --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/build-with-arcgis-maps-sdk-for-unity --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Build with ArcGIS Maps SDK for Unity

ArcGIS Maps SDK for Unity is a Unity plugin for using real-world maps and 3D ArcGIS content in interactive 3D and XR experiences. Use it to bring geospatial data into Unity scenes through Map Creator, SDK Components, or the C# API.

## Application requirements

If the application's development requirements are unclear, use the `gather-arcgis-application-requirements` skill to review project context and clarify consequential unknowns before proceeding. Then apply this skill's technology-specific guidance, reusing requirements already clear from the request or project.

## ArcGIS account requirements

Developers must have one of the following ArcGIS accounts to create applications: ArcGIS Location Platform (free), or ArcGIS Online or ArcGIS Enterprise with a Creator, Professional, or Professional Plus user type. The account's user type, role, and privileges provide access to different resources and operations.

## Authentication

DO NOT SKIP: Refer to the `follow-arcgis-authentication-patterns` skill for ArcGIS authentication requirements, including the appropriate type of authentication for different audiences, use cases, and types of application. If the skill is not available, search the project for any existing authentication patterns, and if none are found, query the Esri MCP server for developer documentation for authentication best practices.

## Installation and setup

1. Before creating or upgrading a project, check the [system requirements](https://developers.arcgis.com/unity/system-requirements/) for the SDK release in use. Verify Unity, render pipeline, and target-platform support.
2. Use HDRP or URP; the built-in render pipeline is unsupported. Check the setup guide for compatible render-pipeline package versions.
3. Install from the [Unity Asset Store](https://assetstore.unity.com/packages/tools/integration/arcgis-maps-sdk-for-unity-258537) or [SDK downloads](https://developers.arcgis.com/unity/downloads/). For tarballs, use Package Manager's **Add package from tarball**. For existing projects, follow the [setup guide](https://developers.arcgis.com/unity/install-and-set-up/add-the-plugin-to-an-existing-project/).
4. Import **Sample Content** if useful. Configure the scene with Map Creator, SDK Components, or the C# API according to the task.
5. Configure ArcGIS access using the authentication guidance above; keep credentials out of source control.
6. For upgrades, follow the [upgrade guide](https://developers.arcgis.com/unity/install-and-set-up/upgrade-to-a-new-plugin-version/) and recheck project compatibility.

## How to query documentation

Installing this skill individually does not configure **Esri MCP server for developer documentation** (`esri-mcp-server-for-developer-documentation`). Add that server at `https://developers-mcp.arcgis.com/mcp` using your client's MCP settings, or install the full **ArcGIS SDKs and APIs** plugin (`arcgis-sdks-and-apis-plugin`). If the MCP server is unavailable, consult the linked official Esri documentation.

Documentation can be queried using the Esri MCP server for developer documentation (`esri-mcp-server-for-developer-documentation`):
```
https://developers-mcp.arcgis.com/mcp
```
Use the `search_esri_developer_docs` tool to surface authoritative documentation pages with `unity-sdk` as the `focus_area` parameter in addition to a specified `search_term`. Use the `fetch_esri_developer_docs` tool with the `page_url` parameter set to return the full content of a documentation page in Markdown format. 

Clearly indicate any recommendations and assumptions that are not grounded in the official documentation. If the MCP server is unavailable, consult official documentation URLs below.

## Documentation links

- [ArcGIS Maps SDK for Unity](https://developers.arcgis.com/unity/) - Start here for an overview, key features, and links to current resources.
- [API reference](https://developers.arcgis.com/unity/api-reference/) - Look up SDK classes, methods, and properties before generating or changing C# code.
- [Install and setup](https://developers.arcgis.com/unity/install-and-set-up/) - Follow the current project creation and plugin installation workflow.
- [System requirements](https://developers.arcgis.com/unity/system-requirements/) - Check SDK-version-specific development and deployment compatibility.
- [Scene setting options](https://developers.arcgis.com/unity/install-and-set-up/scene-setting-options/) - Decide between Map Creator, Components, and the C# API.
- [Display a map with Map Creator](https://developers.arcgis.com/unity/maps/tutorials/display-a-map-ui/) - Create and configure a map through the editor UI.
- [Display a map with Components](https://developers.arcgis.com/unity/maps/tutorials/display-a-map-comp/) - Set up a map and layers using Unity components.
- [Display a map with the C# API](https://developers.arcgis.com/unity/maps/tutorials/display-a-map-api/) - Build a map setup through code.
- [Spatial references](https://developers.arcgis.com/unity/spatial-reference-and-data-analysis/spatial-references/) - Check coordinate-system support and map/data spatial-reference compatibility.
- [FAQ](https://developers.arcgis.com/unity/faq/) - Troubleshoot common data-loading and scene issues.
- [Sample code](https://developers.arcgis.com/unity/sample-code/) - Find working examples for SDK features.

## Patterns and guidelines

- Use C# scripting with the SDK API as the default approach; Use the SDK API directly; do not assume SDK Components are required. Use Map Creator for no-code map setup or SDK Components for GameObject-based integration. Components can also be configured through C#.
- Choose a global or local scene for the geographic extent. Ensure map and layer spatial references are compatible; the first layer may determine the map spatial reference.
- Preserve the ArcGIS Map's HPRoot setup, which addresses floating-point precision limits.
- For missing data, inspect view-state logs, camera extent, layer source, authentication, supported formats, and spatial-reference compatibility.
- Use the matching API reference and existing SDK components or samples instead of recreating SDK behavior.
- Check target-device requirements; editor success does not validate a player build.

## Validation process

- [ ] Check Unity, render pipeline, target platform, and installed SDK against the system requirements.
- [ ] Confirm the package and required Components are available; run a relevant sample when useful.
- [ ] Verify authentication and access to required ArcGIS resources without exposing credentials.
- [ ] Run the scene; check camera position, layer loading, Unity Console, and view-state logs.
- [ ] If data is missing, check spatial references, supported formats, and global/local scene choice.
- [ ] Build and test for the target platform when available.
