No install, no sign-up
Create a keystore or CSR without Android Studio, keytool, or Keychain Access, and find a UDID without a Mac. Everything runs from your browser.
Mobile signing toolkit
Free mobile app signing tools for iOS and Android
Generate an Android keystore online, create an iOS distribution certificate without a Mac, and find an iPhone UDID in seconds. Built for teams shipping Capacitor, Ionic, React Native, Flutter, and native mobile apps, with step-by-step guides for Gradle, Xcode, fastlane, CI, and cloud builds.
Tool stack
Choose the tool that matches your release bottleneck
Each tool comes with a step-by-step guide, troubleshooting tips, and an FAQ, so you know exactly what to do with the output.
CSR + private key
iOS Certificate Generator
Create an iOS distribution or development certificate without a Mac: get an Apple-ready CSR and private key, then a .p12 for signing.
Open toolProfile service
iOS UDID Finder
Find an iPhone or iPad UDID in seconds from Safari, without a Mac or iTunes, plus model, serial, and iOS version.
Open toolPKCS#12 keystore
Android Keystore Generator
Generate an Android keystore online without Android Studio: a PKCS#12 release key with SHA-1 and SHA-256 fingerprints for Google Play.
Open toolReal, ready-to-use files
Download a PKCS#12 keystore, an Apple-ready CSR and private key, or copy a device UDID. Each tool explains exactly where the output goes next.
Nothing stored
Signing files and device details are generated on demand and returned straight to you. Keys, passwords, and identifiers are never saved to a database.
Release operations
Why these pages exist
Mobile teams still lose time on the same tasks every week: generating a fresh CSR for Apple Developer, collecting a tester UDID from a physical iPhone, or creating a keystore that matches the Play signing pipeline. Search results often send people into outdated CLI examples or forum threads with half the steps missing.
These pages are meant to be operational. The interface produces the output immediately, while the surrounding content answers the follow-up questions that usually appear right after generation: where the file goes next, which values must be stored securely, and how the asset fits into CI or cloud build systems.
If you are running a cross-platform release process, pair these tools with the Capgo native build docs and keep the generated signing assets in a secure secret manager instead of committing them to Git.