Token images and IPFS

Prepare the image

The uploader accepts non-animated PNG, JPEG, or WebP images up to 2 MiB (2,097,152 bytes), with dimensions no larger than 4096 × 4096 pixels. The backend decodes the file and checks its actual format, not just its extension.

Use an image you have the right to publish. Remove personal information and embedded metadata before uploading. The service validates the file but does not promise to strip its metadata.

Upload before launching

Enter the final token name and ticker, choose the image, then confirm that the image and metadata may be stored on public IPFS. Upload to IPFS sends the file to FiatEx’s backend, which uses its server-side Pinata credentials to pin the image and a JSON metadata file.

{
  "name": "Your token name",
  "symbol": "YOURTICKER",
  "image": "ipfs://IMAGE_CID"
}

This is a format example; IMAGE_CID is a placeholder. The app puts the real metadata URI into your launch form. Changing the name or ticker clears that URI so you do not launch with mismatched metadata.

If the image uploads but the metadata step fails, the image may already be public. Retry before launching. Removing an image from the form does not remove a previously pinned file from IPFS.

What stays fixed, and what can fail

The token’s metadata URI cannot be changed after launch. An IPFS content identifier identifies specific content, but continued retrieval depends on someone keeping that content available. A gateway can be slow or unavailable.

Manual HTTPS metadata can change at its host even when the onchain URI stays fixed. Only supported IPFS metadata and image identifiers are rendered by the app’s current image reader.

Uploads are disabled when Pinata is not configured. Upload origin is a server setting naming the allowed website, currently the launchpad domain. It is not another field a creator must fill in, and an origin check is not user authentication.