Fliporium

Fliporium Docs

Install the app, create private rooms, send files, and understand the privacy model.

Install and first run

Download fliporium.exe and save it anywhere on a Windows 10 or Windows 11 machine. Fliporium is a portable app, so there is no installer and no account setup.

On first run, Fliporium creates a local identity key and a fliporium-data folder next to the executable. That folder holds local chat history, settings, identity material, and received files. Keep it if you want to keep the same local identity and history.

Fliporium uses the WebView2 runtime that ships with modern Windows systems. No JavaScript toolchain, browser extension, or separate service is required on your machine.

Interface terms

A few labels appear throughout the app:

The Floor
The home view where peers, rooms, and the invite-link entry field are shown.
Room
An invite-only group space with its own message history and room encryption key.
Direct message
A one-to-one conversation with a peer.
Flip
The app's term for sending a file. Received files are saved under fliporium-data/inbox/.
Backstage
The settings area for theme, sound, Twin Mode, help, and local data reset.
Twin Mode
A pairing mode for syncing direct-message history between two of your own devices.

Invite a peer

Rooms are joined by invite link. Anyone with the complete link can enter the room, so treat invite links as secrets.

Step 1: create a room

  1. Open The Floor.
  2. Click the + control next to Rooms.
  3. Name the room.

Step 2: copy the invite link

In the room, use copy invite link. The link looks like https://fliporium.com/join#r=...&k=.... The room id and room key live in the fragment after #.

Browsers do not send URL fragments to servers. The join page can help a user copy the full link, but the server does not receive the room key from that fragment. Anyone who has the full link can join the room, so rotate to a new room if a link is shared too broadly.

Step 3: what the invited peer does

  1. Download and run fliporium.exe.
  2. Paste the invite link into the invite field on The Floor.
  3. Join the room. Once peers are online, Fliporium negotiates a WebRTC connection.

Direct messages

Click a peer on The Floor to open a one-to-one conversation. Type in the composer and press Enter to send.

Message formatting

Message actions

Private rooms

A room is a group conversation with its own invite link, room key, member list, and message history. Create rooms for small groups where every member should have access to the same conversation and file transfers.

To add a member to an existing room, copy the room invite link and send it to that person through a channel you trust. There is no server-side account permission list; possession of the complete invite link is what grants room access.

File transfer

Drag a file onto an open conversation or use the file control in the app. Fliporium sends the file over the encrypted peer-to-peer data channel and stores received files under fliporium-data/inbox/.

Twin Mode

Twin Mode pairs two of your own devices so direct-message history can be replayed between them. Use it when you run Fliporium on a laptop and a desktop and want both local histories to stay aligned.

  1. On device A, open Backstage and configure Twin Mode for device B.
  2. On device B, configure Twin Mode for device A.
  3. After pairing, direct messages sent or received on one device are replayed to the other.

Press Ctrl + K to open search. Fliporium searches local message history across peers and rooms using SQLite full-text search, then opens the selected result in context.

Settings

Theme
Choose dark or light mode. The first run follows the operating system preference.
Sounds
Enable or disable the notification chime for incoming messages.
Twin Mode
Pair another device that belongs to you.
Help
Replay the first-run tour.
Danger zone
Reset local Fliporium data on this device. This removes local identity, settings, history, and received files from this machine only.

Privacy and server visibility

The signaling server helps peers discover each other and exchange WebRTC setup messages. It can see connection metadata such as room ids, routing ids, display names announced by devices, timing, and whether a TURN relay is in use. It does not receive the room key from invite-link fragments and cannot read encrypted room content.

Live messages and files move between devices when a peer-to-peer path is available. Offline messages and relayed traffic are still encrypted before the server handles them. See the privacy page for the full data handling details.

Troubleshooting

Fliporium opens but stays on "starting"

The app could not reach the signaling server. Check your network connection and look at fliporium-data/fliporium.log for the most recent connection error.

A peer is listed but appears offline

That peer has been seen before but is not currently connected. Messages sent while the peer is offline can be delivered later through the encrypted offline backlog when the peer reconnects.

A file transfer did not start

Confirm that the recipient is online and reachable. File transfers require both sides to be connected at the same time.

I want to reset this device

Use the local reset option in Backstage, or close the app and remove the fliporium-data folder. Other peers' local copies are not affected.

FAQ

Is Fliporium open source?

Yes. The source is available at github.com/aivrar/fliporium-p2p under the MIT license.

Does Fliporium work on macOS or Linux?

Not yet. Windows is the current supported desktop target. The networking core is cross-platform, so other desktop builds are possible later.

Does Fliporium work on phones?

Not currently. Fliporium is a Windows desktop app.

What happens if the signaling server goes offline?

Already-connected peers can continue using their existing peer-to-peer connection. New joins, rejoins, offline delivery, and new WebRTC negotiation depend on the signaling server being available.

Do messages go through Fliporium's servers?

Live messages normally travel directly between devices. Offline delivery and restrictive-network relays can pass through server infrastructure, but the server handles encrypted ciphertext rather than plaintext content.

Can I run my own signaling server?

Yes. The signaling server is a standalone Go service, and the app can be pointed at another instance for self-hosted deployments.

Ready to try it? Download Fliporium for Windows or return to the homepage.