defold · ekharkunov · Aug 11, 2026
diff --git a/docs/en/manuals/bob.md b/docs/en/manuals/bob.md
@@ -204,7 +204,7 @@ Available platforms and architectures:
 : iOS 64 bit. By default, `--architectures` argument value is `arm64-ios`.
 
 `armv7-android`
-: Android with available 32 bit `armv7-android` and 64 bit `arm64-android` architectures. By default, `--architectures` argument value is `armv7-android,arm64-android`.
+: Android with available 32 bit `armv7-android`, 64 bit `arm64-android` and 64 bit `x86_64-android` architectures. By default, `--architectures` argument value is `armv7-android,arm64-android`. The `x86_64-android` architecture is opt-in (mainly useful for Android emulators, ChromeOS and Windows Subsystem for Android) and must be added explicitly.
 
 `wasm-web`
 : HTML5 with available `wasm-web` and `wasm_pthread-web` architectures. By default, `--architectures` argument value is `wasm-web`.

diff --git a/docs/en/manuals/debugging-native-code.md b/docs/en/manuals/debugging-native-code.md
@@ -91,7 +91,7 @@ It is very important that your save the debug symbols somewhere for each public
 
 
 ### Uploading symbols to Google Play
-You can [upload the debug symbols to Google Play](https://developer.android.com/studio/build/shrink-code#android_gradle_plugin_version_40_or_earlier_and_other_build_systems) so that any crashes logged in Google Play will show symbolicated call stacks. Zip the contents of the `projecttitle.apk.symbols/lib/` bundle output folder. The folder includes one or more sub folders with architecture names such as `arm64-v8a` and `armeabi-v7a`.
+You can [upload the debug symbols to Google Play](https://developer.android.com/studio/build/shrink-code#android_gradle_plugin_version_40_or_earlier_and_other_build_systems) so that any crashes logged in Google Play will show symbolicated call stacks. Zip the contents of the `projecttitle.apk.symbols/lib/` bundle output folder. The folder includes one or more sub folders with architecture names such as `arm64-v8a`, `armeabi-v7a` and `x86_64`.
 
 
 ### Symbolicate an Android callstack

diff --git a/docs/en/manuals/extensions-best-practices.md b/docs/en/manuals/extensions-best-practices.md
@@ -65,7 +65,7 @@ In certain places, the platform architecture is used as a folder name, to know w
 
 The current list is:
 
-    arm64-ios, armv7-ios, x86_64-ios, arm64-android, armv7-android, x86_64-linux, x86_64-osx, x86_64-win32, x86-win32
+    arm64-ios, armv7-ios, x86_64-ios, arm64-android, armv7-android, x86_64-android, x86_64-linux, x86_64-osx, x86_64-win32, x86-win32
 
 So for instance, put platform specific libraries under:
 

diff --git a/docs/en/manuals/optimization-size.md b/docs/en/manuals/optimization-size.md
@@ -95,6 +95,8 @@ Android builds must support both 32-bit and 64-bit CPU architectures. When you [
 
 ![Signing Android bundle](images/android/sign_bundle.png)
 
+By default a bundle includes the `armv7-android` and `arm64-android` architectures. A third architecture, `x86_64-android`, is available but not included by default since it is mainly useful for Android emulators, ChromeOS and Windows Subsystem for Android rather than for physical devices. Leave it unchecked to keep the bundle size down unless you specifically need to target one of those environments.
+
 Google Play has support for [multiple APKs](https://developer.android.com/google/play/publishing/multiple-apks) per release of a game, which means that you can reduce the application size by generating two APKs, one per CPU architecture, and uploading both to Google Play.
 
 You can also make use of a combination of [APK Expansion Files](https://developer.android.com/google/play/expansion-files) and [Live Update content](/manuals/live-update) thanks to the [APKX extension in the Asset Portal](https://defold.com/assets/apkx/).
diff --git a/docs/en/shared/platforms.md b/docs/en/shared/platforms.md
@@ -1,3 +1,3 @@
 Supported platforms are `ios`, `android`, `osx`, `win32`, `linux`, `web`.
 
-Supported `arc-platform` pairs are `arm64-ios`, `x86_64-ios`, `armv7-android`, `arm64-android`, `arm64-osx`, `x86_64-osx`, `x86-win32`, `x86_64-win32`, `arm64-linux`, `x86_64-linux`, `wasm-web` and `wasm_pthread-web`.
+Supported `arc-platform` pairs are `arm64-ios`, `x86_64-ios`, `armv7-android`, `arm64-android`, `x86_64-android`, `arm64-osx`, `x86_64-osx`, `x86-win32`, `x86_64-win32`, `arm64-linux`, `x86_64-linux`, `wasm-web` and `wasm_pthread-web`.
diff --git a/docs/es/manuals/bob.md b/docs/es/manuals/bob.md
@@ -204,7 +204,7 @@ Plataformas y arquitecturas disponibles:
 : iOS 64 bits. De forma predeterminada, el valor del argumento `--architectures` es `arm64-ios`.
 
 `armv7-android`
-: Android con las arquitecturas disponibles `armv7-android` de 32 bits y `arm64-android` de 64 bits. De forma predeterminada, el valor del argumento `--architectures` es `armv7-android,arm64-android`.
+: Android con las arquitecturas disponibles `armv7-android` de 32 bits, `arm64-android` de 64 bits y `x86_64-android` de 64 bits. De forma predeterminada, el valor del argumento `--architectures` es `armv7-android,arm64-android`. La arquitectura `x86_64-android` es opcional (principalmente útil para emuladores de Android, ChromeOS y Windows Subsystem for Android) y debe añadirse explícitamente.
 
 `wasm-web`
 : HTML5 con las arquitecturas disponibles `wasm-web` y `wasm_pthread-web`. De forma predeterminada, el valor del argumento `--architectures` es `wasm-web`.

diff --git a/docs/es/manuals/debugging-native-code.md b/docs/es/manuals/debugging-native-code.md
@@ -91,7 +91,7 @@ Es muy importante que guardes los símbolos de depuración en algún lugar para
 
 
 ### Subir símbolos a Google Play {#uploading-symbols-to-google-play}
-Puedes [subir los símbolos de depuración a Google Play](https://developer.android.com/studio/build/shrink-code#android_gradle_plugin_version_40_or_earlier_and_other_build_systems) para que cualquier crash registrado en Google Play muestre callstacks simbolizados. Comprime en un zip el contenido de la carpeta de salida del bundle `projecttitle.apk.symbols/lib/`. La carpeta incluye una o más subcarpetas con nombres de arquitectura como `arm64-v8a` y `armeabi-v7a`.
+Puedes [subir los símbolos de depuración a Google Play](https://developer.android.com/studio/build/shrink-code#android_gradle_plugin_version_40_or_earlier_and_other_build_systems) para que cualquier crash registrado en Google Play muestre callstacks simbolizados. Comprime en un zip el contenido de la carpeta de salida del bundle `projecttitle.apk.symbols/lib/`. La carpeta incluye una o más subcarpetas con nombres de arquitectura como `arm64-v8a`, `armeabi-v7a` y `x86_64`.
 
 
 ### Simbolizar un callstack de Android {#symbolicate-an-android-callstack}

diff --git a/docs/es/manuals/extensions-best-practices.md b/docs/es/manuals/extensions-best-practices.md
@@ -65,7 +65,7 @@ En ciertos lugares, la arquitectura de la plataforma se usa como nombre de carpe
 
 La lista actual es:
 
-    arm64-ios, armv7-ios, x86_64-ios, arm64-android, armv7-android, x86_64-linux, x86_64-osx, x86_64-win32, x86-win32
+    arm64-ios, armv7-ios, x86_64-ios, arm64-android, armv7-android, x86_64-android, x86_64-linux, x86_64-osx, x86_64-win32, x86-win32
 
 Por ejemplo, coloca las bibliotecas específicas de plataforma en:
 

diff --git a/docs/es/manuals/optimization-size.md b/docs/es/manuals/optimization-size.md
@@ -95,6 +95,8 @@ Las builds de Android deben admitir arquitecturas de CPU de 32 y 64 bits. Cuando
 
 ![Signing Android bundle](images/android/sign_bundle.png)
 
+De forma predeterminada, un bundle incluye las arquitecturas `armv7-android` y `arm64-android`. Existe una tercera arquitectura, `x86_64-android`, disponible pero no incluida por defecto, ya que resulta principalmente útil para emuladores de Android, ChromeOS y Windows Subsystem for Android, en lugar de para dispositivos físicos. Déjala sin marcar para mantener reducido el tamaño del bundle, a menos que necesites específicamente apuntar a uno de esos entornos.
+
 Google Play admite [múltiples APK](https://developer.android.com/google/play/publishing/multiple-apks) por release de un juego, lo que significa que puedes reducir el tamaño de la aplicación generando dos APK, uno por arquitectura de CPU, y subiendo ambos a Google Play.
 
 También puedes usar una combinación de [APK Expansion Files](https://developer.android.com/google/play/expansion-files) y [contenido de Live Update](/manuals/live-update) gracias a la [extensión APKX en el Asset Portal](https://defold.com/assets/apkx/).
diff --git a/docs/es/shared/platforms.md b/docs/es/shared/platforms.md
@@ -1,3 +1,3 @@
 Las plataformas compatibles son `ios`, `android`, `osx`, `win32`, `linux`, `web`.
 
-Los pares `arc-platform` compatibles son `arm64-ios`, `x86_64-ios`, `armv7-android`, `arm64-android`, `arm64-osx`, `x86_64-osx`, `x86-win32`, `x86_64-win32`, `arm64-linux`, `x86_64-linux`, `wasm-web` y `wasm_pthread-web`.
+Los pares `arc-platform` compatibles son `arm64-ios`, `x86_64-ios`, `armv7-android`, `arm64-android`, `x86_64-android`, `arm64-osx`, `x86_64-osx`, `x86-win32`, `x86_64-win32`, `arm64-linux`, `x86_64-linux`, `wasm-web` y `wasm_pthread-web`.
diff --git a/docs/ko/manuals/bob.md b/docs/ko/manuals/bob.md
@@ -204,7 +204,7 @@ usage: bob [options] [commands]
 : iOS 64 bit. 기본적으로 `--architectures` 인자 값은 `arm64-ios`입니다.
 
 `armv7-android`
-: 사용 가능한 32 bit `armv7-android` 및 64 bit `arm64-android` 아키텍처가 있는 Android입니다. 기본적으로 `--architectures` 인자 값은 `armv7-android,arm64-android`입니다.
+: 사용 가능한 32 bit `armv7-android`, 64 bit `arm64-android` 및 64 bit `x86_64-android` 아키텍처가 있는 Android입니다. 기본적으로 `--architectures` 인자 값은 `armv7-android,arm64-android`입니다. `x86_64-android` 아키텍처는 선택적으로 추가할 수 있으며(주로 Android 에뮬레이터, ChromeOS, Windows Subsystem for Android에 유용함) 명시적으로 추가해야 합니다.
 
 `wasm-web`
 : 사용 가능한 `wasm-web` 및 `wasm_pthread-web` 아키텍처가 있는 HTML5입니다. 기본적으로 `--architectures` 인자 값은 `wasm-web`입니다.

diff --git a/docs/ko/manuals/debugging-native-code.md b/docs/ko/manuals/debugging-native-code.md
@@ -91,7 +91,7 @@ iTunes에서 앱 컨테이너를 보거나 다운로드할 수 있습니다.
 
 
 ### Google Play에 심볼 업로드하기
-Google Play에 기록된 크래시가 심볼리케이트된 콜스택으로 표시되도록 [디버그 심볼을 Google Play에 업로드](https://developer.android.com/studio/build/shrink-code#android_gradle_plugin_version_40_or_earlier_and_other_build_systems)할 수 있습니다. `projecttitle.apk.symbols/lib/` 번들 출력 폴더의 내용을 zip으로 압축하세요. 이 폴더에는 `arm64-v8a`, `armeabi-v7a` 같은 아키텍처 이름을 가진 하위 폴더가 하나 이상 포함됩니다.
+Google Play에 기록된 크래시가 심볼리케이트된 콜스택으로 표시되도록 [디버그 심볼을 Google Play에 업로드](https://developer.android.com/studio/build/shrink-code#android_gradle_plugin_version_40_or_earlier_and_other_build_systems)할 수 있습니다. `projecttitle.apk.symbols/lib/` 번들 출력 폴더의 내용을 zip으로 압축하세요. 이 폴더에는 `arm64-v8a`, `armeabi-v7a`, `x86_64` 같은 아키텍처 이름을 가진 하위 폴더가 하나 이상 포함됩니다.
 
 
 ### Android 콜스택 심볼리케이트하기

diff --git a/docs/ko/manuals/extensions-best-practices.md b/docs/ko/manuals/extensions-best-practices.md
@@ -65,7 +65,7 @@ Lua API는 하나만 있어야 하며, 그 구현도 하나만 있어야 합니
 
 현재 목록은 다음과 같습니다.
 
-    arm64-ios, armv7-ios, x86_64-ios, arm64-android, armv7-android, x86_64-linux, x86_64-osx, x86_64-win32, x86-win32
+    arm64-ios, armv7-ios, x86_64-ios, arm64-android, armv7-android, x86_64-android, x86_64-linux, x86_64-osx, x86_64-win32, x86-win32
 
 예를 들어 플랫폼별 라이브러리는 다음 위치에 넣습니다.
 

diff --git a/docs/ko/manuals/optimization-size.md b/docs/ko/manuals/optimization-size.md
@@ -95,6 +95,8 @@ Android 빌드는 32비트와 64비트 CPU 아키텍처를 모두 지원해야
 
 ![Android 번들 서명](images/android/sign_bundle.png)
 
+기본적으로 번들에는 `armv7-android` 및 `arm64-android` 아키텍처가 포함됩니다. 세 번째 아키텍처인 `x86_64-android`도 사용할 수 있지만 기본적으로는 포함되지 않습니다. 이는 실제 기기보다는 Android 에뮬레이터, ChromeOS, Windows Subsystem for Android에서 주로 유용하기 때문입니다. 이러한 환경을 특별히 대상으로 해야 하는 경우가 아니라면 체크 해제된 상태로 두어 번들 크기를 줄이세요.
+
 Google Play는 게임 릴리스당 [여러 APK](https://developer.android.com/google/play/publishing/multiple-apks)를 지원합니다. 즉, CPU 아키텍처마다 하나씩 두 개의 APK를 생성하고 둘 다 Google Play에 업로드하여 어플리케이션 크기를 줄일 수 있습니다.
 
 [APK Expansion Files](https://developer.android.com/google/play/expansion-files)와 [Live Update 컨텐츠](/manuals/live-update)를 조합해 사용할 수도 있으며, 이는 [Asset Portal의 APKX extension](https://defold.com/assets/apkx/) 덕분에 가능합니다.
diff --git a/docs/ko/shared/platforms.md b/docs/ko/shared/platforms.md
@@ -1,3 +1,3 @@
 지원되는 플랫폼은 `ios`, `android`, `osx`, `win32`, `linux`, `web`입니다.
 
-지원되는 `arc-platform` 쌍은 `arm64-ios`, `x86_64-ios`, `armv7-android`, `arm64-android`, `arm64-osx`, `x86_64-osx`, `x86-win32`, `x86_64-win32`, `arm64-linux`, `x86_64-linux`, `wasm-web`, `wasm_pthread-web`입니다.
+지원되는 `arc-platform` 쌍은 `arm64-ios`, `x86_64-ios`, `armv7-android`, `arm64-android`, `x86_64-android`, `arm64-osx`, `x86_64-osx`, `x86-win32`, `x86_64-win32`, `arm64-linux`, `x86_64-linux`, `wasm-web`, `wasm_pthread-web`입니다.
diff --git a/docs/pl/manuals/bob.md b/docs/pl/manuals/bob.md
@@ -204,7 +204,7 @@ Dostępne platformy i architektury:
 : iOS 64-bit. Domyślnie wartość argumentu `--architectures` to `arm64-ios`.
 
 `armv7-android`
-: Android z dostępnymi 32-bitowymi architekturami `armv7-android` i 64-bitowymi `arm64-android`. Domyślnie wartość argumentu `--architectures` to `armv7-android,arm64-android`.
+: Android z dostępnymi 32-bitowymi architekturami `armv7-android`, 64-bitowymi `arm64-android` i 64-bitowymi `x86_64-android`. Domyślnie wartość argumentu `--architectures` to `armv7-android,arm64-android`. Architektura `x86_64-android` jest opcjonalna (przydatna głównie dla emulatorów Androida, ChromeOS i Windows Subsystem for Android) i musi zostać dodana jawnie.
 
 `wasm-web`
 : HTML5 z dostępnymi architekturami `wasm-web` i `wasm_pthread-web`. Domyślnie wartość argumentu `--architectures` to `wasm-web`.

diff --git a/docs/pl/manuals/debugging-native-code.md b/docs/pl/manuals/debugging-native-code.md
@@ -91,7 +91,7 @@ Bardzo ważne jest, aby zachować symbole debugowe dla każdego publicznego wyda
 
 
 ### Przesyłanie symboli do Google Play
-Możesz [przesłać symbole debugowe do Google Play](https://developer.android.com/studio/build/shrink-code#android_gradle_plugin_version_40_or_earlier_and_other_build_systems), aby wszystkie awarie zarejestrowane w Google Play pokazywały zsymbolikowane stosy wywołań. Spakuj do ZIP-a zawartość katalogu wyjściowego bundla `projecttitle.apk.symbols/lib/`. Katalog zawiera jeden lub więcej podkatalogów o nazwach architektur, takich jak `arm64-v8a` i `armeabi-v7a`.
+Możesz [przesłać symbole debugowe do Google Play](https://developer.android.com/studio/build/shrink-code#android_gradle_plugin_version_40_or_earlier_and_other_build_systems), aby wszystkie awarie zarejestrowane w Google Play pokazywały zsymbolikowane stosy wywołań. Spakuj do ZIP-a zawartość katalogu wyjściowego bundla `projecttitle.apk.symbols/lib/`. Katalog zawiera jeden lub więcej podkatalogów o nazwach architektur, takich jak `arm64-v8a`, `armeabi-v7a` i `x86_64`.
 
 
 ### Zsymbolikuj stos wywołań z Androida

diff --git a/docs/pl/manuals/extensions-best-practices.md b/docs/pl/manuals/extensions-best-practices.md
@@ -65,7 +65,7 @@ W niektórych miejscach architektura platformy jest używana jako nazwa folderu,
 
 Aktualna lista to:
 
-    arm64-ios, armv7-ios, x86_64-ios, arm64-android, armv7-android, x86_64-linux, x86_64-osx, x86_64-win32, x86-win32
+    arm64-ios, armv7-ios, x86_64-ios, arm64-android, armv7-android, x86_64-android, x86_64-linux, x86_64-osx, x86_64-win32, x86-win32
 
 Na przykład biblioteki specyficzne dla platformy umieszczaj w:
 

diff --git a/docs/pl/manuals/optimization-size.md b/docs/pl/manuals/optimization-size.md
@@ -95,6 +95,8 @@ Kompilacje na Androida muszą obsługiwać zarówno 32-bitowe, jak i 64-bitowe a
 
 ![Podpisywanie pakietu Android](images/android/sign_bundle.png)
 
+Domyślnie pakiet zawiera architektury `armv7-android` i `arm64-android`. Dostępna jest trzecia architektura, `x86_64-android`, ale nie jest dołączana domyślnie, ponieważ jest przydatna głównie dla emulatorów Androida, ChromeOS i Windows Subsystem for Android, a nie dla fizycznych urządzeń. Pozostaw ją odznaczoną, aby zmniejszyć rozmiar pakietu, chyba że musisz celować w jedno z tych środowisk.
+
 Google Play obsługuje [wiele APK](https://developer.android.com/google/play/publishing/multiple-apks) dla jednego wydania gry, co oznacza, że możesz zmniejszyć rozmiar aplikacji, generując dwa APK, po jednym dla każdej architektury CPU, i przesyłając oba do Google Play.
 
 Możesz też skorzystać z połączenia [APK Expansion Files](https://developer.android.com/google/play/expansion-files) oraz zawartości [Live Update](/manuals/live-update) dzięki rozszerzeniu [APKX](https://defold.com/assets/apkx/) w Asset Portal.
diff --git a/docs/pl/shared/platforms.md b/docs/pl/shared/platforms.md
@@ -1,3 +1,3 @@
 Obsługiwane platformy to `ios`, `android`, `osx`, `win32`, `linux`, `web`.
 
-Obsługiwane pary `arc-platform` to `arm64-ios`, `x86_64-ios`, `armv7-android`, `arm64-android`, `arm64-osx`, `x86_64-osx`, `x86-win32`, `x86_64-win32`, `arm64-linux`, `x86_64-linux`, `wasm-web` oraz `wasm_pthread-web`.
+Obsługiwane pary `arc-platform` to `arm64-ios`, `x86_64-ios`, `armv7-android`, `arm64-android`, `x86_64-android`, `arm64-osx`, `x86_64-osx`, `x86-win32`, `x86_64-win32`, `arm64-linux`, `x86_64-linux`, `wasm-web` oraz `wasm_pthread-web`.
diff --git a/docs/pt/manuals/bob.md b/docs/pt/manuals/bob.md
@@ -204,7 +204,7 @@ Plataformas e arquiteturas disponíveis:
 : iOS 64 bit. Por padrão, o valor do argumento `--architectures` é `arm64-ios`.
 
 `armv7-android`
-: Android com arquiteturas disponíveis de 32 bits `armv7-android` e 64 bits `arm64-android`. Por padrão, o valor do argumento `--architectures` é `armv7-android,arm64-android`.
+: Android com arquiteturas disponíveis de 32 bits `armv7-android`, 64 bits `arm64-android` e 64 bits `x86_64-android`. Por padrão, o valor do argumento `--architectures` é `armv7-android,arm64-android`. A arquitetura `x86_64-android` é opcional (útil principalmente para emuladores Android, ChromeOS e Windows Subsystem for Android) e deve ser adicionada explicitamente.
 
 `wasm-web`
 : HTML5 com arquiteturas disponíveis `wasm-web` e `wasm_pthread-web`. Por padrão, o valor do argumento `--architectures` é `wasm-web`.

diff --git a/docs/pt/manuals/debugging-native-code.md b/docs/pt/manuals/debugging-native-code.md
@@ -91,7 +91,7 @@ Se você obtiver uma callstack de um arquivo `_crash` ou de um [arquivo de log](
 
 
 ### Enviando símbolos para o Google Play
-Você pode [enviar os símbolos de debug para o Google Play](https://developer.android.com/studio/build/shrink-code#android_gradle_plugin_version_40_or_earlier_and_other_build_systems) para que quaisquer travamentos registrados no Google Play mostrem call stacks simbolicadas. Compacte o conteúdo da pasta de saída de pacote `projecttitle.apk.symbols/lib/`. A pasta inclui uma ou mais subpastas com nomes de arquitetura, como `arm64-v8a` e `armeabi-v7a`.
+Você pode [enviar os símbolos de debug para o Google Play](https://developer.android.com/studio/build/shrink-code#android_gradle_plugin_version_40_or_earlier_and_other_build_systems) para que quaisquer travamentos registrados no Google Play mostrem call stacks simbolicadas. Compacte o conteúdo da pasta de saída de pacote `projecttitle.apk.symbols/lib/`. A pasta inclui uma ou mais subpastas com nomes de arquitetura, como `arm64-v8a`, `armeabi-v7a` e `x86_64`.
 
 
 ### Simbolicar uma callstack do Android

diff --git a/docs/pt/manuals/extensions-best-practices.md b/docs/pt/manuals/extensions-best-practices.md
@@ -65,7 +65,7 @@ Em certos lugares, a arquitetura da plataforma é usada como nome de pasta, para
 
 A lista atual é:
 
-    arm64-ios, armv7-ios, x86_64-ios, arm64-android, armv7-android, x86_64-linux, x86_64-osx, x86_64-win32, x86-win32
+    arm64-ios, armv7-ios, x86_64-ios, arm64-android, armv7-android, x86_64-android, x86_64-linux, x86_64-osx, x86_64-win32, x86-win32
 
 Então, por exemplo, coloque bibliotecas específicas de plataforma em: