Move sticker packs between Signal, Telegram and WhatsApp
  • Dart 65%
  • Go 8.7%
  • CSS 7.4%
  • Shell 5.6%
  • Kotlin 5.3%
  • Other 8%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
manzari 6620369067 Move the promo engine to apppage 81fb0e3
The engine picks up the source-code channel, which turns the source_url set
in _config.yml into a download button and a footer link and replaces the
footer link added by hand. It also brings the optional assetlinks.json and
per-project webfonts, which Kisscut does not use. en.yml gains the strings
the source channel needs.
2026-11-21 00:57:41 +01:00
app Release 0.2.0 2026-11-20 23:06:33 +01:00
deploy Add Kisscut: move sticker packs between Signal, Telegram and WhatsApp 2026-11-19 22:17:18 +01:00
fastlane/metadata/android/en-US Add the Play Store listing texts 2026-11-21 00:17:29 +01:00
packages Let packs be edited after import 2026-11-20 21:59:43 +01:00
promo Move the promo engine to apppage 81fb0e3 2026-11-21 00:57:41 +01:00
server Add Kisscut: move sticker packs between Signal, Telegram and WhatsApp 2026-11-19 22:17:18 +01:00
tool Add the Play Store icon and feature graphic 2026-11-20 22:38:15 +01:00
.gitignore Add Kisscut: move sticker packs between Signal, Telegram and WhatsApp 2026-11-19 22:17:18 +01:00
analysis_options.yaml Add Kisscut: move sticker packs between Signal, Telegram and WhatsApp 2026-11-19 22:17:18 +01:00
codemagic.yaml Add Codemagic workflows for Play uploads 2026-11-21 00:10:04 +01:00
LICENSE Add Kisscut: move sticker packs between Signal, Telegram and WhatsApp 2026-11-19 22:17:18 +01:00
Makefile Add the Play Store icon and feature graphic 2026-11-20 22:38:15 +01:00
pubspec.lock Add Kisscut: move sticker packs between Signal, Telegram and WhatsApp 2026-11-19 22:17:18 +01:00
pubspec.yaml Add Kisscut: move sticker packs between Signal, Telegram and WhatsApp 2026-11-19 22:17:18 +01:00
README.md Write the README header links as markdown 2026-11-21 00:53:14 +01:00

Kisscut

Move sticker packs between Signal, Telegram and WhatsApp.

The library of imported packs A pack, ready to go to WhatsApp or Telegram A pack of 45 stickers, split in two for WhatsApp

The packs on these screens are made up for the screenshots.

Share a pack link to the app; it downloads the pack into its own library and, when asked, converts the stickers on the phone and hands them to a messenger through its official import API.

Packs come in from Packs go out to
Signal pack link WhatsApp
Telegram pack link (needs the fetch server) Telegram
  • Converted on the phone. Each sticker is resized and compressed on the device to the limits of the messenger it goes to. For WhatsApp that is 512 × 512 WebP under 100 KB.
  • Big packs, split evenly. WhatsApp takes 3 to 30 stickers per pack; a larger pack is split into even parts, added one by one.
  • The messengers' own import. WhatsApp and Telegram receive the stickers through the import they offer to other apps. No account login and no unofficial client.
  • Yours to change. Once a pack is in the library it is Kisscut's own, and can be changed: renamed, reordered, trimmed, given other emoji and another cover. Where it came from is recorded, and only used to recognise the same pack when it is imported again; every pack goes to every target.
  • No account, no tracking. No sign-up, no analytics, no ads. The library stays on the phone.

Status: milestone 1 of four. Still stickers only; animated ones are counted and left out.

Install

Kisscut runs on Android 7.0 and later. Add the manzari.dev repository to the F-Droid app, then install Kisscut from it; updates arrive the same way.

Without a phone, the same pipeline runs from a terminal: make cli builds it, and Working on it shows how to use it.

Layout

Path What
packages/kisscut_core Pure Dart: link parsing, Signal and Telegram download, conversion, WhatsApp and Telegram export, on-disk library and the edits to a pack
packages/kisscut_cli The same pipeline from a terminal
app Flutter app; the Android side holds the WhatsApp content provider and both hand-off intents
server Go service that holds a Telegram bot token and proxies sticker set downloads
deploy Coolify stack for the server
promo Landing page: its content, and a copy of the apppage engine in promo/engine
fastlane/metadata/android Store listing texts: the short and the full description

Working on it

Everything runs in Docker; nothing is installed on the host.

make test            # core, CLI, app, Android provider (JVM) and server
make test-core ARGS="--run-skipped --tags network"   # also import a real Signal pack
make test-android    # debug app on an emulator, needs KVM: import, convert, query the WhatsApp provider
make cli             # build/kisscut
make apk             # debug APK
make apk-release     # needs app/android/key.properties
make server-up       # fetch server on localhost:8080, needs server/.env
make promo-up        # landing page on localhost:8888, with placeholder legal pages
make promo-shots     # render the app's screens into promo/images

Try the pipeline without a phone:

build/kisscut import 'https://signal.art/addstickers/#pack_id=…&pack_key=…'
build/kisscut list
build/kisscut show <pack-id>
build/kisscut emoji <pack-id> 🐱🐶 1 3-7
build/kisscut move <pack-id> 12 --before 1
build/kisscut export <pack-id> --to whatsapp

build/kisscut --help lists the rest: rename, cover, remove and restore.

Telegram links need a fetch server: pass --server http://localhost:8080 or set KISSCUT_SERVER. The app takes the address in Settings, or at build time with --dart-define=KISSCUT_SERVER=https://….

How the library stores stickers

  • One form for stills. Every still is stored once as WebP with its pixels untouched: a WebP is kept byte for byte, a PNG is re-encoded losslessly. Nothing is resized or compressed on the way in.
  • Converted on demand. An export is made from that copy each time, so a second export is as good as the first. A sticker that already meets the target's limits is handed over as it is.
  • Animated stickers stay in the format they arrived in until they are supported.
  • On disk: packs/<id>/pack.json and packs/<id>/stickers/, exports in exports/<target>/<id>_<k>/. A library written by 0.1.x is rewritten to this layout on first start; its exports are left alone, so packs already added to WhatsApp keep working.

Editing a pack

  • What can change: the name and author, the order, the emoji of each sticker (up to three; WhatsApp takes all, Telegram the first), the cover, and which stickers are in the pack. The cover is the pack's picture in the library and the icon of the WhatsApp pack that holds it.
  • Nothing is deleted. A removed sticker moves to removed in pack.json and its file stays, so it can be put back.
  • Exports notice. Each export records a fingerprint of what it was made from. Once the pack differs, the app offers an update; updating a WhatsApp export raises its image_data_version.
  • Importing again replaces a pack with a fresh copy, so a pack that was edited is only replaced after asking (--replace in the CLI).
  • One place. The edits are functions on StickerPack in packages/kisscut_core/lib/src/edit.dart, stored through Library.edit; the app and the CLI both call those.

How the hand-offs work

  • WhatsApp reads packs from the app's content provider (dev.manzari.kisscut.stickercontentprovider), which serves whatever is in library/exports/whatsapp/. WhatsApp allows 3 to 30 stickers per pack, so larger packs are split evenly and added one by one. The split is made anew on each export, so removing or moving stickers can shift them between those packs.
  • Telegram receives the files and one emoji per sticker through its CREATE_STICKER_PACK intent, 120 stickers at a time.
  • Signal downloads need no server. cdn.signal.org is signed by Signal's own CA, which the core carries and trusts for that host only.

Landing page

kisscut.manzari.dev is built from promo/ by the apppage engine, a copy of which is in promo/engine: texts in promo/i18n/en.yml, links and Impressum data in promo/_config.yml, colours in promo/brand.css, and the privacy policy and terms from promo/engrossify.yaml. promo/compose.yaml is the deployment and names the one secret its build needs.

The images on the page are the app's real screens, rendered by make promo-shots with sticker packs drawn for the purpose, since real packs are other people's artwork. The download buttons come from the channels set in promo/_config.yml, at present fdroid_url; with none set they read "Coming soon".

Licence

GPL-3.0-or-later. See LICENSE.

Kisscut is not affiliated with Signal, Telegram or WhatsApp.