JPEG
On-chain image sender · SPL Memo · base64

Put a tiny image on-chain
and send it to your friend.

Splits a JPG into chunks, base64-encodes each chunk into a real SPL Memo instruction, and sends one transaction per chunk to the wallet you name. They read it back and rebuild the file in their browser.

Every transaction is exactly what the cost preview says. There is no separate “authorization” step, and nothing is pre-approved.

Why base64: the SPL Memo program requires valid UTF-8 and rejects arbitrary binary with Invalid UTF-8, from byte N. Raw JPEG bytes are not valid UTF-8, so each chunk is base64-encoded (~33% overhead) to make it valid ASCII. That overhead is why per-chunk capacity is small.
This runs on Solana mainnet with real SOL. Anything you send is written on-chain permanently and publicly — it cannot be deleted, by you or anyone else. Send only images you're happy to have public forever, and only to someone who is expecting them.
01 — Imagejpg only
Drop a JPG, or click to browse
anything over … is auto-scaled to fit
02 — Destinationwhere it lands
Send to a friend's wallet
Adds a 1-lamport transfer so the image lands in their transaction history.
Archive to my own wallet
No transfer instruction at all — slightly cheaper, and it stays in your own history.
Friend's wallet address
Their account must already exist on-chain. Solana requires new accounts to hold the rent-exempt minimum (~0.0009 SOL), so a 1-lamport transfer to a never-used address fails with “insufficient funds for rent”. Checked automatically below. Send only to people expecting it — blasting strangers is dusting, and wallets filter it as spam.
03 — Wallet, fees & sendyou approve every transaction
Not connected
Phantom shows you every transaction before you approve — nothing is pre-authorized
Priority fee — micro-lamports per compute unit
Pick a file to see the real cost.
memo MemoSq4gqABAXKb96qnH8TysNcWxMyWCqXgDLGmfcHr format solimg1|tid|idx|total|base64

Retrieve an image from a wallet

Scans a wallet's recent transaction history for memo chunks and rebuilds any complete transfer it finds.

04 — Reassembleread it back
Wallet address
Signatures to scan — higher is slower and heavier on RPC
On-chain data is permanent and public