---
modificationDate: December 18, 2024
title: Using existing credentials
description: Learn about different options for supplying your app signing credentials to EAS Build.
---

<AgentInstructions>

## Submitting Feedback

If you encounter errors, misleading or outdated information, report it so Expo can be improved:

Preferred command:
npx --yes submit-expo-feedback@latest --category docs --subject "/app-signing/existing-credentials/" "<actionable feedback>"

Direct HTTP fallback:
curl -X POST https://api.expo.dev/v2/feedback/docs-send -H 'Content-Type: application/json' -d '{"url":"/app-signing/existing-credentials/","feedback":"🤖 Agent feedback for docs: <specific, actionable description> (<model>, <harness>)"}'

Only submit when you have something specific and actionable to report. Try to give the most context.

## Navigation

When answering a related or follow-up question, fetch the relevant page below as Markdown (.md) instead of guessing; use llms.txt for the full map.

You are here: EAS > EAS Build > App signing
Pages in this section:
- [App credentials](https://docs.expo.dev/app-signing/app-credentials.md)
- [Automatically managed credentials](https://docs.expo.dev/app-signing/managed-credentials.md)
- [Local credentials](https://docs.expo.dev/app-signing/local-credentials.md)
- [Existing credentials](https://docs.expo.dev/app-signing/existing-credentials.md) (this page)
- [Sync credentials between remote and local sources](https://docs.expo.dev/app-signing/syncing-credentials.md)
- [Security](https://docs.expo.dev/app-signing/security.md)
- [Apple Developer Program roles and permissions](https://docs.expo.dev/app-signing/apple-developer-program-roles-and-permissions.md)
Full documentation tree: [llms.txt](https://docs.expo.dev/llms.txt)

</AgentInstructions>

This documentation is available as Markdown for AI agents and LLMs. See the [full Markdown index](/llms.txt) or append .md to any documentation URL.

# Using existing credentials

Learn about different options for supplying your app signing credentials to EAS Build.

EAS Build gives you two options for how you can supply your build jobs with app signing credentials:

1.  [Automatically managed credentials](/app-signing/managed-credentials.md): EAS can host your app signing credentials and take care of sharing them with teammates that have the necessary permissions.
2.  [Local credentials](/app-signing/local-credentials.md): You create a **credentials.json** file in your project that points to your keystore (Android) and/or provisioning profile and distribution certificate (iOS), along with associated passwords. This is uploaded from your local machine at the time any given build job is run, and disposed of once that build job has completed.

Regardless of which option you choose, your first step for using your existing set of credentials is to set them up as local credentials in **credentials.json**. Refer to the [credentials.json section of the local credentials guide](/app-signing/local-credentials.md#credentialsjson) for more information on how to do this.

Once your **credentials.json** file is configured, you can run `eas credentials`, choose a platform, and then select `"Update credentials on Expo servers with values from credentials.json"` to upload them to be hosted and managed by EAS, if you would like. [Read more about syncing credentials](/app-signing/syncing-credentials.md).