Google Play 图标设计规范
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
Google Play 上的应用和游戏现已采用新的图标系统，可根据 Google Play 的各种界面布局、设备类型和设备调整各种开发者效果图，进而为 Google Play 打造简洁一致的外观。
统一的图标形状在视觉上更具吸引力，也让画面更加一目了然，有助于将用户的注意力集中到图片本身，而非图标的外在形状。统一的形状还能解决随机空白区域导致的对齐问题，从而更好地呈现标题、评分和价格等周边信息。
本页介绍了为应用创建 Google Play 商品详情素材资源时需要遵循的指南。例如，Google Play 会为您的应用图标动态呈现圆角和阴影，因此您在原始素材资源中可省去这些设计。
重要提示：本页仅说明了 Google Play 图标相关信息，如果您有兴趣详细了解如何制作 APK 启动器图标，请参考以下资源：
- Android 自适应图标
请遵循这些 APK 图标指南，了解如何制作在 Android 8.0（API 级别 26）中推出的自适应启动器图标。
- 产品图标
了解产品图标的 Material Design 原则，包括图标设计、形状、规范和处理指南。
创建素材资源
本部分介绍了您为 Google Play 中的应用创建可视化素材资源时应遵循的一些指南。
属性
您可以用图标图片填充整个素材资源空间，也可以设计徽标等图片元素并放置到框线网格上。放置图片时，请以框线作为参考，但这不是硬性规定。
制作图片时，请确保图片符合以下要求：
- 最终尺寸：512 x 512 像素
- 格式：32 位 PNG
- 颜色空间：sRGB
- 文件大小上限：1024KB
- 形状：完整正方形 - Google Play 会动态处理遮盖部分。半径相当于图标大小的 20%。
- 阴影：无 - Google Play 会动态处理阴影。请参阅下文的“阴影”部分，了解如何在图片中添加阴影。
素材资源上传后，Google Play 会动态应用圆角遮盖部分和阴影，确保所有应用/游戏图标的设计保持一致。
左侧显示的是新的图标素材资源。下方右侧三张图片显示的是 Google Play 动态处理该图标的过程。
大小
处理极简图片时，请将整个素材资源空间用作背景。
放置徽标等图片元素时，请使用框线作为参考。
Google Play 以动态方式应用阴影和圆角的最终效果
请勿强制将您的徽标或图片铺满整个素材资源空间。建议您改用框线网格来调整。
cancel
错误
请勿将具有强烈色彩的品牌和图片强制转换为全宽配置
check_circle
正确
请改为在框线上放置自由格式的图标图片
一般来说，插图图片以全宽图标呈现的效果比较好。
cancel
错误
请勿将插图图片缩小到框线范围内
check_circle
正确
利用整个素材资源空间，使您的图片占据整个图标范围
以下是会误导用户和违反 Play 开发者政策的图标元素示例。请避免以下所有做法，并参阅 Google Play 的“元数据”政策和“用户评分、评价和安装次数”政策，以获取进一步的指导。
cancel
错误做法
请勿使用文字或图形元素来表明排名
cancel
错误做法
请勿使用文字或图形元素来推广优惠活动或诱使用户安装
cancel
错误做法
请勿使用文字或图形元素来表明是否有参与 Play 计划
cancel
错误做法
请勿使用可能会误导用户的文字或图形元素
阴影
图标上传后，Google Play 会以动态方式在最终图标周围添加阴影。
在图标图片中添加阴影时，请遵循 Google Material 指南，以便与 Android 平台设计保持一致。
check_circle
正确
您可以在图片内设计阴影和光线
角半径
Google Play 会以动态方式应用圆角半径。这可以确保图标针对不同界面布局调整大小时，能够保持一致。半径相当于图标大小的 20%。
check_circle
正确
尽可能将图片填满整个素材资源空间
品牌适应
如果徽标的形状非常重要，请勿强制将图片调整为全宽配置，
而应将其放置在新的框线网格上。
从左到右依次为：原始图标素材资源、新版图标素材资源（按建议进行调整）、在 Google Play 上呈现的新图标。
如果可能，请为素材资源选择适合您品牌的背景颜色，不要保留任何透明部分。透明的素材资源会显示 Google Play 界面的背景颜色。
从左到右依次为：原始图标素材资源、新版图标素材资源（按建议进行调整）、在 Google Play 上呈现的新图标。
如果徽标四周没有明显的形状来确定其边界，请将其放到全宽背景中。
从左到右依次为：原始图标素材资源、新版图标素材资源（按建议进行调整）、在 Google Play 上呈现的新图标。
如果您的图片设计足够灵活，可以考虑调整图片，以便充分利用素材资源的大小。如果无法做到这一点，可改回将徽标放置在框线网格上。
从左到右依次为：原始图标素材资源、新版图标素材资源（按建议进行调整）、在 Google Play 上呈现的新图标。
旧版模式
原有的图标素材资源如未根据新规范更新，最终都会迁移到旧版模式，并依据框线网格缩小为 75% 的大小（512 * 0.75 = 384 像素）。
自 2019 年 5 月起，系统将不允许按原来的规范上传图标。有关详情，请参阅时间线。
原始图标素材资源会自动转换为旧版模式的素材资源，并依据新框线网格缩小为 75% 的大小。
面向 API 用户的说明
API 用户的迁移日期略有不同，但最终结果都是在 2019 年 6 月 24 日之前需要使所有图标遵守新规范，否则自动转换为“旧版模式”。
在 2019 年 6 月 17 日之前，开发者必须使用 Play 管理中心对其图标应用新规范。所有对 Edits.images: upload 的调用都将应用在 Play 管理中心中配置的规范。无法通过 API 应用新规范。如果仍然应用旧规范，则 Edits.images: upload 调用可能会出错，并且该特定图标的错误消息会将您指向此规范。使用 Play 管理中心应用新规范后，您可以重试 Edits.images: upload 调用。您可能需要多次重试该调用，它才能成功。
从 2019 年 6 月 17 日开始，对 Edits.images: upload 的所有 API 调用都会自动对图标应用新规范。2019 年 6 月 17 日之后，您只能上传符合新规范的图标。
下载设计模板和资源
要开始使用，请下载下面的其中一个素材资源模板：
本页面上的内容和代码示例受内容许可部分所述许可的限制。Java 和 OpenJDK 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2023-09-25。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["没有我需要的信息","missingTheInformationINeed","thumb-down"],["太复杂/步骤太多","tooComplicatedTooManySteps","thumb-down"],["内容需要更新","outOfDate","thumb-down"],["翻译问题","translationIssue","thumb-down"],["示例/代码问题","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2023-09-25。"],[],[],null,["# Google Play icon design specifications\n\n\u003cbr /\u003e\n\nApps \\& Games on Google Play are adopting a new icon system to better fit diverse\ndeveloper artwork to Google Play's various UI layouts, form factors, and\ndevices, as well as to bring consistency and a cleaner look to Google Play.\n\nUniformed shapes are visually more appealing and easier to digest. They help\nusers focus on the artwork, as opposed to the shape. They fix alignment issues\ncaused by random open space to better present surrounding information, such as\nthe title, rating, and price.\n\n\nFreeform -- original format \n\nUniformed -- new format\n\n\u003cbr /\u003e\n\nThis page describes the guidelines you should follow when creating assets for\nyour app's listing on Google Play. For example, because Google Play dynamically\nrenders rounded corners and drop shadows for your app icons, you should omit\nthem from your original assets.\n\n**Important:** If instead you're interested in learning more about creating APK\nlauncher icons, which are separate from the Google Play icons described on this\npage, see the resources below:\n\n- [Android Adaptive Icons](/guide/practices/ui_guidelines/icon_design_adaptive) \n Follow these APK icon guidelines to learn how to create adaptive launcher icons introduced in Android 8.0 (API level 26).\n- [Product icons](https://material.io/design/iconography/product-icons.html) \n Discover Material Design principles for product icons, including guidelines for icon design, shapes, specs, and treatment.\n\nCreating assets\n---------------\n\nThis section describes some guidelines you should follow when creating visual\nassets for your app on Google Play.\n\n### Attributes\n\nIcon artwork can populate the entire asset space, or you can design and position\nartwork elements such as logos onto the keyline grid. When placing your artwork,\nuse keylines as a guideline, not a hard rule.\n\nWhen creating your artwork, ensure it conforms to the following:\n\n- Final size: 512px x 512px\n- Format: 32-bit PNG\n- Color space: sRGB\n- Max file size: 1024KB\n- Shape: Full square -- Google Play dynamically handles masking. Radius will be equivalent to 20% of icon size.\n- Shadow: None -- Google Play dynamically handles shadows. See 'Shadows' section below on including shadows within your artwork.\n\n\nTotal asset size \n\nProduct icon keylines\n\n\u003cbr /\u003e\n\nAfter the asset is uploaded, Google Play dynamically applies the rounded mask\nand shadow to ensure consistency across all app/game icons. \nOn the left-hand side is your new icon asset. The following three images on the right-hand side show Google Play dynamic processing of the icon.\n\n### Sizing\n\nUtilize the full asset space as the background when dealing with minimalistic\nartwork.\n\nUse the keylines as guides for positioning artwork elements (i.e. logos).\n\n\nYour full bleed artwork (final asset) \n\nEnd result with shadows and rounded corners dynamically applied by Google Play\n\n\u003cbr /\u003e\n\nDon't force your logo or artwork to fit the full asset space. Instead, utilize\nthe keyline grid. \ncancel\n\n### Wrong\n\nDon't force drastic brand \\& artwork transformation to full bleed \ncheck_circle\n\n### Right\n\nPlace freeform icon artwork on keylines instead\n\nIllustrated artwork typically works well as a full bleed icon. \ncancel\n\n### Wrong\n\nDon't scale down illustrated artwork onto keylines \ncheck_circle\n\n### Right\n\nUtilize full asset space so your artwork occupies the entire icon\n\nThese are examples of icon elements that mislead users and violate Play's\nDeveloper policies. Avoid all of the following practices, and refer to\nGoogle Play's [metadata policy](https://support.google.com/googleplay/android-developer/answer/9898842?ref_topic=9877064)\nand [user ratings, reviews, and installs policy](https://support.google.com/googleplay/android-developer/answer/9898684?ref_topic=9877064#zippy=%2Cexamples-of-common-violations-in-app-title-icon-or-developer-name)\nfor further guidance. \ncancel\n\n### Don't\n\nDon't use text or graphic elements to indicate ranking \ncancel\n\n### Don't\n\nDon't use text or graphic elements to promote deals or incentivize installs \ncancel\n\n### Don't\n\nDon't use text or graphic elements to indicate participation in a Play program \ncancel\n\n### Don't\n\nDon't use text or graphic elements that can mislead users\n\n### Shadows\n\nGoogle Play will dynamically add a drop shadow around the final icon once\nuploaded.\n\nWhen adding shadows inside your icon artwork, consider consistency with the\nAndroid platform by following Google Material [guidelines](https://material.io/guidelines/style/icons.html#icons-product-icons). \ncancel\n\n### Wrong\n\nDon't add drop shadows to your final asset \ncheck_circle\n\n### Right\n\nYou can create shadows and lighting within the artwork\n\n### Corner radius\n\nGoogle Play dynamically applies corner radius. This ensures consistency when the\nicon is resized across different UI layouts. Radius will be equivalent to 20% of\nicon size. \ncancel\n\n### Wrong\n\nDon't round the edges of your final asset \ncheck_circle\n\n### Right\n\nFill your entire asset with artwork when possible\n\nBrand adaptation\n----------------\n\nIf shapes are a critical part of a logo, do not force the artwork to full bleed.\nInstead place it on the new keyline grid. \nFrom left to right: original icon asset, new icon asset (recommended adaptation), new icon rendered on Google Play.\n\nIf possible, pick a background color for your asset that's appropriate for your\nbrand and doesn't include any transparency. Transparent assets will display the\nbackground color of Google Play UI. \nFrom left to right: original icon asset, new icon asset (recommended adaptation), new icon rendered on Google Play.\n\nIf there is no distinct shape around a logo defining it, place it on a full\nbleed background. \nFrom left to right: original icon asset, new icon asset (recommended adaptation), new icon rendered on Google Play.\n\nIf your artwork is flexible enough, consider tweaking it to fully utilize the\nasset size. If that's not possible, revert to placing the logo on a keyline\ngrid. \nFrom left to right: original icon asset, new icon asset (recommended adaptation), new icon rendered on Google Play.\n\nLegacy mode\n-----------\n\nOriginal icon assets that have not been updated per the new specifications will\neventually be migrated to legacy mode and scaled down 75% to the keyline grid\nsize (512 \\* 0.75 = 384px).\n\nUploading an icon per the original specification will not be allowed as of May\n2019. [See more details on timelines](https://android-developers.googleblog.com/2019/03/introducing-new-google-play-app-and.html). \nOriginal icon assets will be automatically turned into legacy mode assets and be scaled down 75% to new keyline grid.\n\nInstructions for API users\n--------------------------\n\nMigration dates are slightly different for API users, but achieve the same end\nresult of migrating all icons to either the new specification or \"legacy mode\"\nby June 24, 2019.\n\nBefore June 17, 2019, developers must use the Play Console to apply the new\nspecification to their icons. All calls to [Edits.images: upload](https://developers.google.com/android-publisher/api-ref/edits/images/upload)\nwill apply whichever specification is configured in the Play Console. There is\nno way to apply the new specification via API. The `Edits.images: upload` call\nmay error if the old specification is still applied, and the error\nmessage for that specific icon will point you to this specification. After\napplying a new specification using the Play Console, you can retry the\n`Edits.images: upload` call. You may need to retry the call multiple times\nbefore it will succeed.\n\nBeginning on June 17, 2019, all API calls to `Edits.images: upload` will\nautomatically apply the new specification to the icon. Following June 17, 2019,\nyou should only upload icons that are compatible with the new specification.\n\nDownload design templates \\& resources\n--------------------------------------\n\nTo get started, download one of the provided asset templates:\n\n- [Sketch template](https://services.google.com/fh/files/misc/playstore_icon_template.sketch.zip) (.sketch)\n- [Illustrator template](https://services.google.com/fh/files/misc/playstore_icon_template.ai.zip) (.ai)\n- [Photoshop template](https://services.google.com/fh/files/misc/playstore_icon_template.psd.zip) (.psd)"]]
