1---
2title: App stores metadata
3description: Learn how to automate and maintain your app store presence from the command line with EAS Metadata.
4---
5
6import { Terminal } from '~/ui/components/Snippet';
7import { BoxLink } from '~/ui/components/BoxLink';
8import { EasMetadataIcon, LayersTwo02Icon } from '@expo/styleguide-icons';
9
10> **warning** EAS Metadata is in beta and subject to breaking changes.
11
12When submitting your app to app stores, you need to provide metadata. This process is lengthy and is about often about complex topics that don't apply to your app. After the information you provide gets reviewed and if there is any issue with it, you need to restart this process.
13
14**EAS Metadata** enables you to automate and maintain this information from the command line instead of going through multiple forms in the app store dashboards. It can also instantly identify well-known app store restrictions that could trigger a rejection after a lengthy review queue. This guide shows how to use EAS Metadata to automate and maintain your app store presence.
15
16## Prerequisites
17
18EAS Metadata is available starting from EAS CLI >= 0.54.0, and currently **only supports the Apple App Store**.
19
20> Using VS Code? Install the [VS Code Expo plugin](https://github.com/expo/vscode-expo#readme) for auto-complete, suggestions, and warnings in your **store.config.json** files.
21
22## Create a store config
23
24EAS Metadata uses [store.config.json](/eas/metadata/config/) file to hold all the information you want to upload to the app stores. This file is located at the root of your Expo project.
25
26Create a new **store.config.json** file at the root of your project directory as shown in the example below:
27
28```json store.config.json
29{
30  "configVersion": 0,
31  "apple": {
32    "info": {
33      "en-US": {
34        "title": "Awesome App",
35        "subtitle": "Your self-made awesome app",
36        "description": "The most awesome app you've ever seen",
37        "keywords": ["awesome", "app"],
38        "marketingUrl": "https://example.com/en/promo",
39        "supportUrl": "https://example.com/en/support",
40        "privacyPolicyUrl": "https://example.com/en/privacy"
41      }
42    }
43  }
44}
45```
46
47The above example file contains JSON schema. Replace the example values with your own. It is usually contains your app's `title`, `subtitle` , `description`, `keywords`, and `marketingUrl` and so on.
48
49**An important thing to remember from the above example is the `configVersion` property.** It helps with versioning changes that are not backward compatible.
50
51> For more information on properties that can be defined in **store.config.json**, see [Schema for EAS Metadata](/eas/metadata/schema/#config-schema).
52
53## Upload the store config
54
55> Before pushing the store.config.json to the app stores, you must upload a new binary of your app. See [App Store submissions](/deploy/submit-to-app-stores/) for more information. After the binary is submitted and processed, you can continue with the step below.
56
57After you have created the **store.config.json** file and added the necessary information related to your app, you can push the store config to the app stores by running the command:
58
59<Terminal cmd={['$ eas metadata:push']} />
60
61If EAS Metadata runs into any issues with your store config, it will warn you when running this command. When there are no errors, or you confirm to push it with possible issues, it will try to upload as much as possible.
62
63You can also re-use this command when you modify the **store.config.json** file and want to push the latest changes to the app stores.
64
65## Next steps
66
67<BoxLink
68  title="Instant updates with EAS Update"
69  description="Learn how to automate and maintain your app store presence from the command line with EAS Metadata."
70  Icon={LayersTwo02Icon}
71  href="/deploy/instant-updates/"
72/>
73
74<BoxLink
75  title="EAS Metadata schema"
76  description="A reference of store config in EAS Metadata."
77  Icon={EasMetadataIcon}
78  href="/eas/metadata/schema/"
79/>
80
81<BoxLink
82  title="Static and dynamic configurations with EAS Metadata"
83  description="Learn about different ways to configure EAS Metadata."
84  Icon={EasMetadataIcon}
85  href="/eas/metadata/config/"
86/>
87