On the Images & Multimedia or Binary File(s) tab in your app details, click on the FTP instructions and naming convention link to obtain the app-specific naming conventions you will need to upload via FTP.

FTP Upload Steps

 1.  Select the app whose file(s) you will be uploading using the dropdown

2.  Use the generated name list to rename any assets over 100 MB to the specific file name provided—this file name is how Amazon will know what app and asset field to apply the file

3.  Using the FTP client of your choice, login and upload your renamed files using the specified FTP server and username—if needed, reset your password to have a new one sent to you

4.  You’re almost done! Simply review and submit your app once your files appear uploaded

Allow up to 20 minutes for an e-mail confirmation that your assets are processed and available. You will also receive an e-mail if the uploaded asset is invalid or misnamed. E-mails will be sent to the e-mail address you have provided us in your Distribution Portal profile. Once the asset has been uploaded, finish any remaining steps and review your content one last time. After you have satisfied all the asset requirements, you will be able to submit your app to have it reviewed for inclusion in the store.

More about the FTP Naming Convention

Every app has a unique application ID (appId below) that is a required part of the filename when you upload via FTP. Including the package name after the application ID is optional—add the package name only if it helps you organize your files.

Small icon (114 x 114 pixels):  appId-AD-ICON.png  or  appId-package.name-AD-ICON.png

EXAMPLE:  M0A2KAXJX4CATH-AD-ICON.png or M0A2KAXJX4CATH-com.example.mobile.app-AD-ICON.png

Large icon (512 x 512 pixels):  appId-AD-THUMB.png  or  appId-package.name-AD-THUMB.png

EXAMPLE: M0A2KAXJX4CATH-AD-THUMB.png OR M0A2KAXJX4CATH-com.example.mobile.app-AD-THUMB.png

Screenshots (1024 x 600px or 800 x 480 pixels): appId-AD-SHOTXX.png orappId-package.name-AD-SHOTXX.png where XX is an optional numerical index of the image

EXAMPLE: M0A2KAXJX4CATH-AD-SHOT.png, M0A2KAXJX4CATH-com.example.mobile.app-AD-SHOT.png, M0A2KAXJX4CATH-com.example.mobile.app-AD-SHOT1.png, M0A2KAXJX4CATH-com.example.mobile.app-AD-SHOT05.png

Promotional image (1024 x 500 pixels, landscape only): appId-AD-PROMO.png or appId-package.name-AD-PROMO.png

EXAMPLE: M0A2KAXJX4CATH-AD-PROMO.png or M0A2KAXJX4CATH-com.example.mobile.app-AD-PROMO.png

Video(s): appId-AD-VIDEOXX.png or appId-package.name-AD-VIDEOXX.avi where XX is an optional numerical index of the video

EXAMPLE: M0A2KAXJX4CATH-com.example.mobile.app-AD-VIDEO.avi,M0A2KAXJX4CATH-com.example.mobile.app-AD-VIDEO1.avi,M0A2KAXJX4CATH-com.example.mobile.app-AD-VIDEO05.avi

Binary file/APK:

Signed by Amazon (recommended)

With DRM: appId-<binary alias>.apk  or  appId-package.name-<binary alias>.apk

EXAMPLE: M0A2KAXJX4CATH-my_alias.apk orM0A2KAXJX4CATH-com.example.mobile.app-my_alias.apk

Without DRM: appId-<binary alias>-nodrm.apk or appId-package.name-<binary alias>-nodrm.apk appId-<binary alias>-nodrm.apk or appId-package.name-<binary alias>-nodrm.apk

EXAMPLE: M0A2KAXJX4CATH-my_alias-nodrm.apkor M0A2KAXJX4CATH-com.example.mobile.app-my_alias-nodrm.apk

Signed by you

Unsigned binary with DRM: appId-<binary alias>-precert.apk or appId-package.name-<binary alias>-precert.apk

EXAMPLE: M0A2KAXJX4CATH-my_alias-precert.apk orM0A2KAXJX4CATH-com.example.mobile.app-my_alias-precert.apk

Unsigned binary without DRM: appId-<binary alias>-precert-nodrm.apk or appId-package.name-<binary alias>-precert-nodrm.apk

EXAMPLE: M0A2KAXJX4CATH-my_alias-precert-nodrm.apk  or  M0A2KAXJX4CATH-com.example.mobile.app-my_alias-precert-nodrm.apk

Signed binary: appId-<binary alias>-mycert.apk or appId-package.name-<binary alias>-mycert.apk

EXAMPLE: M0A2KAXJX4CATH-my_alias-signed.apk