Packpour for App Store Connect
Chrome side panel · local-first

One locale pack,
every App Store Connect field filled.

Packpour reads a multilingual TXT or Markdown pack, then pours every labeled value into the matching field on the current App Store Connect locale page. Save and Submit stay manual.

TXT · Markdown · scoped to appstoreconnect.apple.com · never auto-submits

appstoreconnect.apple.com
My App: Metadata filler

macOS App Version 0.1.0

Save

The assets and metadata below appear on your app's product page.

English (U.S.) ▾
Promotional Text Edit
A Chrome side panel that pours locale packs into App Store Connect.
66

Description
Packpour imports multilingual metadata packs and fills App Store Connect locale fields after a direct user action. Save and Submit stay manual.
148

Keywords
localization, ASO, metadata, multilingual, Packpour
54 / 100
Packpour v0.1.0
Locale pack
en-US English
Fill App Store Connect page
✓ Poured into 6 fields
10 locale packs loaded
en zh-CN zh-TW ja ko fr de es pt it

Why Packpour

Not full automation — faster localization with safer review boundaries.

🗂

One pack pours many fields

Import one TXT/MD file — Packpour pours every labeled value into the matching field in the current locale page.

🎯

Smart field matching

Tries label, placeholder, aria-label, name, and id. Falls back to focused-field fill whenever detection misses.

🔒

Local-first, review manual

Packs stay in Chrome local storage. Password, payment, and token-looking fields are always skipped. Save and Submit stay in your hands.

🌐

Ten languages

English, 简/繁中文, 日本語, 한국어, Français, Deutsch, Español, Português, Italiano. Auto-detects browser locale; switch anytime in Settings.

How it works

Four steps from raw metadata to filled fields.

1

Generate locale files

Use the built-in AI prompt to generate one TXT block per locale with stable field labels.

2

Import packs

Bring in multiple TXT or Markdown files at once. Their file names become your locale switcher.

3

Open the target page

Packpour only runs on the active appstoreconnect.apple.com tab and targets visible editable metadata fields.

4

Pour, inspect, then save

Use bulk fill or focused-field fill. Packpour never clicks Save, Publish, or Submit for Review.

Packpour vs manual filling

Removing the repetitive steps around multilingual metadata, not replacing your judgment.

Feature
Packpour
Typical manual flow
Import multiple locale packs at once
copy / paste file by file
Maps fields to the current locale page
manual field switching
Focused-field fallback
redo the whole field manually
Keyword byte-limit tracking
count manually
Auto-submit disabled by design
depends on discipline
Ten UI languages out of the box
1–2
Runs locally — no backend
not guaranteed

Install

No Chrome Web Store account needed. Download, unzip, load.

From source

Best for contributors or people iterating on the field-matching logic.

  1. Clone github.com/hooosberg/Packpour
  2. Open chrome://extensions and toggle Developer mode
  3. Click Load unpacked and pick the local/ folder
  4. Open any App Store Connect locale page
Open on GitHub ↗

Quick answers

Does Packpour submit metadata automatically?

No. It fills visible editable fields only. Save, Publish, and Submit for Review always stay manual.

Does it work outside App Store Connect?

No. Packpour is intentionally scoped to appstoreconnect.apple.com.

Where are my imported locale packs stored?

Locally, in your browser's Chrome storage. Nothing is sent to any server.

Can I use both TXT and Markdown files?

Yes. The parser accepts both structured TXT and Markdown packs.

How do I add a new language?

Copy _locales/en/ to a new locale code, translate messages.json, and add the same block to popup.js's TRANSLATIONS map. Open a PR and we'll ship it.

Is Packpour free for my team?

Yes. MIT License — free for personal and team use. If you want to contribute translations or features, email zikedece@proton.me.

More Works

Creative tools from the same developer