A free bill splitting app for restaurants, flatmates and trips, and it works offline. Put in what everyone paid, and Splitover works out who owes whom — then settles the whole group up in the fewest possible payments. No account, nothing to install.
Name the trip, pick a currency, and type in everyone who is coming. Nobody needs to be invited before you can start — names are enough.
Add each expense as it happens: who paid, how much, and who it was for. Split it evenly, by exact amounts, by shares, or item by item off the receipt.
Splitover nets everyone off and shows the shortest list of payments that clears the trip. Mark one as paid and everyone on the trip sees it.
Splito is the idea; Splitover is one of two apps built on it. Both split group expenses and settle everyone up in the fewest payments — they differ in how they look and in a few of the features. Splitover is this one.
Yes. Splitover is free to use, with no ads, no paid tier and no limit on how many trips or people you add.
No, because there is no paid version to hold anything back for. Search, the category chart, itemised bills and the CSV export are simply there, and there is no daily cap on how many expenses you can add.
No. There is no signup, no password and no email to hand over. Open it and start a trip.
No. It runs in a browser, so whoever you send it to can open it and start. You can add it to your home screen if you would rather it opened like an app and kept working with the radio off, but nobody has to.
Yes. Splitover is built offline-first, so you can add expenses and read the balances with no connection at all — on a flight, underground, or abroad with data switched off. What you added goes out to the rest of the trip the next time you have signal.
It splits the bill and works out the shortest set of payments that clears everyone, but it does not move money itself and is not linked to a bank. You pay however you normally would — UPI, cash, a transfer — and record it here, and the balances update.
It covers the same job — group expenses, settled in the fewest payments — without an account, without ads and without a paid tier, and it keeps working offline. Splitwise has been around far longer and has apps on both stores; Splitover runs in a browser, so you can start in the time it takes to type the first expense.
It nets everyone off against each other and then finds the smallest set of payments that clears every balance. Four people owing each other in a circle usually settles in two transfers rather than six.
Yes. Send them an invite link. They open it, pick which name in the trip is theirs, and can add their own expenses from then on.
No, and this is deliberate. A currency is a label on the trip and amounts are never rescaled behind your back, so you can only switch between currencies that use the same number of decimal places.
Yes. Split by exact amounts, so a rent of 1200 goes 800 and 400. Or by percentage, or by shares, which is the quick way to say the big room counts double. Whichever you choose, the parts add up to the total.
Yes. Choose By item, type each line off the receipt, and tick who had it. Somebody who only had a starter pays for a starter.
Add them under Tax, service and tip on an itemised bill. Each charge is spread by share to begin with, meaning in proportion to what each person actually ordered, and you can switch one to an even split instead, which is usually what you want for a tip.
No, and that is a decision rather than a gap. A misread receipt produces confident wrong numbers, and hunting for the line it got wrong costs more than typing the bill would have. By item is built to be typed at speed instead: label and amount share a line, Enter starts the next row, and each new row keeps the people from the one above.
Yes, exactly. Nothing is rounded until the very end, so on a long itemised bill no single person quietly absorbs the leftover paise: every share lands within one paisa of the exact figure, and the shares always sum to the total.
You can add somebody at any time, and existing expenses are left alone, so edit any they should have been part of. Removing is the restricted one. Anybody who already appears in an expense or a payment cannot be removed, because the ledger would stop balancing.
Yes, anybody in the trip can correct an expense somebody else added. There is deliberately no lock on it, because the person most likely to want a quiet edit is whoever typed it in the first place. Every version is kept instead, and each change shows who made it.
Yes. Splitover does not move money: you pay however you normally would, then record it here and the balances update. Record the same amount between the same two people twice and it asks whether you really did mean a second payment.
Yes, as a CSV you can open in Excel or Google Sheets. Every person gets a paid column and a share column, so the sheet reproduces the same balances the app shows and you can check them rather than take them on trust.
Yes. Make one trip for the flat and add rent, groceries and the utility bills as they arrive. Nothing has to be marked settled for the balances to stay right, so it can simply keep running.
Signal goes in exactly the places a bill needs splitting: a basement restaurant, a hill road, somebody else’s country on roaming. Splitover is built offline-first, so the expense you add on a flight lands the same way it would at home and reaches everyone else once you are back in range.
There is no signup in front of any of it — no password, no email, no waiting for four other people to make an account before the maths works. It runs in a browser, so whoever you send it to can open it and start, and adding it to the home screen is optional rather than the price of entry.
Splitting one bill is easy. Working out who owes whom after nine days, four cities and thirty-one receipts is not, and it usually gets settled badly — with more transfers than anyone needed to make. Splitover keeps the ledger while the trip is happening, so the end of it is one short list of payments instead of an argument over a notes app.
Splitover is one of two Splito apps, built by thedevstory.
