The internet speed for Tally on Cloud is modest: plan about 0.5 Mbps for each person working at once. Tally recommends a 512 Kbps minimum for virtual use, and Microsoft measures active spreadsheet-style Remote Desktop work at 150–200 Kbps. Any stable 4G or broadband line is enough. Responsiveness depends on latency, ideally under 100 ms.
The short answer: about 0.5 Mbps per person, and latency matters more
With Tally on Cloud, TallyPrime runs on a Windows server in a data centre and you see it through Remote Desktop. If that idea is new, our explainer on what Tally on Cloud is covers the basics. The part that matters here is simple: your company data never travels to your device. Only pictures of the screen come down and your keystrokes go up, which is why the bandwidth needed is small.
Tally's own Tally Virtual User FAQ recommends a connection with a "minimum speed of 512 Kbps" for virtual use. It doesn't say whether that is per user or per connection, so the cautious reading is 512 Kbps for each person working at the same time on one line. That's the number we plan with, and it leaves plenty of room over what Microsoft measures for similar work.
| People working at once on one line | Tally's minimum (512 Kbps each) | Microsoft's active Excel-type figure (150–200 Kbps each) |
|---|---|---|
| 1 (owner on a laptop or phone) | 0.5 Mbps | 0.15–0.2 Mbps |
| 2 (owner and accountant) | 1 Mbps | 0.3–0.4 Mbps |
| 5 (small office) | 2.6 Mbps | 0.75–1 Mbps |
| 10 (busy office or branch) | 5.1 Mbps | 1.5–2 Mbps |
| 20 (head office team) | 10.2 Mbps | 3–4 Mbps |
Simple multiplication of the published figures, not a measurement of any particular connection. Leave headroom for everything else on the same line: video calls, CCTV uploads, phone backups and Windows updates.
Count people per line, not per company. An accountant at home, a salesperson on 4G and you on office broadband each use a different connection, so each line only carries its own users. That is why multi-user Tally on Cloud scales across branches without a big leased line at head office.
Microsoft's RDP figures and Tally's 512 Kbps advice
Remote Desktop Protocol (RDP) is built to send as little as possible. Microsoft's RDP bandwidth guide explains that only the parts of the screen that change are sent, that text, window elements and solid colours use the least bandwidth, and that when nothing changes on screen, nothing is sent. Here is what actually crosses your connection during a TallyPrime session:
Microsoft also publishes typical bandwidth for different kinds of work, measured on a single 1920×1080 monitor in RDP's default graphics mode. We have plotted the upper end of each range on the same scale and added Tally's 512 Kbps recommendation for comparison:
Microsoft didn't test TallyPrime. Our reading is that TallyPrime's screens, which are text, grids and flat colours with no animation, sit with the Word and Excel rows, well below Tally's own 512 Kbps guidance. Treat that as an informed estimate, not a measurement.
What pushes bandwidth up
- Printing. The whole print job travels from the server to your printer. Microsoft's own example is a 200-page printout, which it says uses a significant amount of bandwidth. Our guide to printing from Tally on Cloud shows how to print smarter.
- Copying files. Moving an Excel export or a bank statement between your device and the server uses compressed bulk transfer, roughly like sending a zip file.
- Bigger and more screens. Microsoft notes that a higher display resolution or frame rate raises the bandwidth needed. A 4K monitor or two screens use more than one 1080p laptop display.
- Video or graphics inside the session. Playing a training video on the server, rather than on your own device, is the single heaviest thing you can do.
Two things bring it back down: an idle session is close to zero, and Microsoft says no screen updates are sent while the Remote Desktop window is minimised.
Myth-buster: is your connection enough for Tally on Cloud?
Most worries about internet speed come from three myths. Here is what the published figures say.
"Cloud accounting needs a 100 Mbps plan."
Fact: Tally asks for 512 Kbps. A 100 Mbps line covers Tally's bandwidth guidance for well over a hundred people at once.
"A faster plan will make Tally faster."
Fact: Once Tally's small needs are covered, a faster plan changes little you can feel. The round trip to the server decides how quickly keys appear.
"If the internet cuts out, my entries are lost."
Fact: Saved vouchers live on the server. Your session waits there for you to reconnect.
Now check your own line. Move the sliders to see how much of your connection Tally's 512 Kbps guidance would take up for the number of people sharing it.
Use a real speed-test result from the Wi-Fi or cable your team uses, not the number on your plan.
- Tally's guidance for this team
- 1.5 Mbps
- Microsoft's active-work estimate
- 0.45–0.6 Mbps
Latency vs speed: why a fast plan can still feel slow
Bandwidth is how wide the road is. Latency is how far away the shop is. Every key you press in TallyPrime travels to the server, the server redraws that part of the screen, and the picture travels back. That round trip, measured in milliseconds (ms), is what you feel as lag, and a bigger data plan does nothing to shorten it.
Microsoft's planning guidance for its own cloud desktops asks for a round trip under 150 ms and tells administrators to place servers in the region closest to their users. RDP specialists such as itopia call under 100 ms ideal and say the experience starts to deteriorate above 150 ms. TallyPrime is a keyboard-first program, so the lower end of that range is what you want.
What adds latency
- Distance. A server abroad adds a long round trip to every keystroke. TallyoCloud servers run in a secure data centre in India, with our primary data centre in Mumbai.
- Wi-Fi. Thick walls, a crowded 2.4 GHz band or a router two rooms away add delay and dropped packets. A cable is the simplest fix.
- VPNs. A VPN can route your traffic through another city or country before it reaches the server. You don't need one: the connection to your server is already encrypted.
- A busy line. When someone uploads a large file, or CCTV pushes footage to the cloud, everything else on that connection waits in the queue, including your keystrokes.
- Your ISP's route. Two providers in the same building can take very different paths to the same data centre.
Speed tests can mislead. Public speed tests usually measure to the nearest test server, often in your own city, and headline the download figure. A 300 Mbps result with a low ping tells you about that route, not about the route to the data centre where your TallyPrime runs.
How to check your own latency
- Type, don't download. During a free 7-day trial, open a sales voucher and type a long narration at your normal speed. If characters keep up with your fingers, your latency is fine.
- Look at the connection bar. In Remote Desktop Connection on Windows, the bar at the top of a full-screen session shows a signal-strength icon; select it to see the connection quality.
- Run a ping. Open Command Prompt and type
ping -n 20followed by the address you connect to, orping -c 20on a Mac or Linux. Read the average. Secure servers sometimes ignore ping, so a timeout doesn't always mean a problem; ask our support team to check the route from our side.
We will publish round-trip figures from Indian cities only after we have measured them properly. Until then, the most honest test is your own connection, from your own desk, during the trial.
Tally on 4G, 5G and a phone hotspot
Yes, Tally on Cloud works on 4G, and it is a practical way to check outstandings and approve entries away from the office. The constraint on mobile is rarely speed. It is signal stability: a weak indoor signal, a crowded tower at peak hours or a moving car makes the round trip jump around, and that feels like lag. Connect from a spot with steady coverage and the session behaves like broadband.
Mobile data use is the other question. Using Microsoft's figures, here is the most an hour of continuous activity could use. Real use is lower, because sessions spend much of their time idle.
| Activity level | Bandwidth | Data per hour if it never stops |
|---|---|---|
| Idle session (screen not changing) | 0.3 Kbps | about 0.1 MB |
| Active Excel-type work (Microsoft) | 150–200 Kbps | about 70–90 MB |
| Tally's full 512 Kbps, nonstop | 512 Kbps | about 230 MB |
Calculated as Kbps × 3,600 seconds ÷ 8 bits per byte. Printing, file copies and a large tablet screen add to these figures.
Phones and tablets connect with Microsoft's free Windows App. Keyboard tips, screen sizes and the PDF route for paper copies are in our guide to Tally on mobile.
What happens when your internet drops mid-voucher
This is where Tally on Cloud is gentler than you might expect. TallyPrime isn't running on your device, so your device losing its connection doesn't stop it. Here is the sequence:
- The connection drops. Your screen freezes or Windows App shows a reconnecting message. On the server, TallyPrime carries on exactly where you left it.
- Windows keeps your session. Remote Desktop marks the session as disconnected rather than closing it. Microsoft's session time limits documentation explains that running programs stay active in a disconnected session until a time limit set by the server's administrator.
- You reconnect. Open the connection again, from the same device or another one, and you usually land back on the same screen, often with the half-typed voucher still open. Remote Desktop Connection on Windows also has a "Reconnect if the connection is dropped" option on its Experience tab.
- Accept and carry on. Finish the voucher and accept it as usual. Everything you accepted before the drop was already saved on the server.
Two details matter. First, for security we log off disconnected sessions after a set time, as described in our Tally RDP set-up, so a laptop left at a client's office doesn't leave your books open. If you come back after that, anything you hadn't accepted is gone, though saved data is untouched. Ask support for the limit on your server.
Second, sign out at the end of the day instead of just closing the window. Tally's performance checklist recommends logging off rather than disconnecting, because a disconnected session keeps TallyPrime running. That open copy holds server memory and can count against your licence's limit, as our Tally Virtual User guide explains.
Why a drop can't damage your data. TallyPrime and the company files sit on the same server, so a dropped home or office connection never interrupts a write to your data. The server itself stays online independently of your internet, with a 99.9% uptime target set out in our SLA.
Backup internet for offices, shops and branches
Because Tally on Cloud needs a connection, the sensible move is a second one. It doesn't have to be expensive. Pick the option that matches how much a lost hour of billing costs you.
| Backup option | Best for | Watch out for |
|---|---|---|
| Phone hotspot | Solo users, owners, small shop counters | Battery and your daily data allowance. The session drops for a moment when you switch, then reconnects. |
| Second broadband from a different ISP | Offices with several users | Choose a provider that reaches your building by a different cable or technology, or one cut can take out both. |
| Dual-WAN router with automatic failover | Billing counters and branches that can't stop | Failover still interrupts the session briefly. Users reconnect to the same session. |
| 4G/5G router as the main line | Godowns and sites with poor wired broadband | Mount it where the signal is steadiest, and judge it on latency, not the speed-test number. |
For a multi-branch business, give each branch its own primary line plus a hotspot or 4G router as backup. Every branch works on the same live company data on the server, so an outage at one branch never affects the others or the books.
Does Tally work without internet?
It depends on where TallyPrime runs. TallyPrime installed on your own Windows PC is desktop software, so day-to-day entries and reports work without a connection. There are two catches. Tally's licensing FAQ says the computer must connect to the internet at least once in 30 days, or the licence turns to Educational mode. And the connected features, such as GST filing, e-invoices, e-way bills, Connected Banking and WhatsApp sharing, need both internet and an active TSS.
| How you run TallyPrime | Works with no internet? | What still needs internet |
|---|---|---|
| Installed on your own PC | YesEntries and reports | Licence check at least every 30 days; GST, e-invoice, e-way bill and banking features |
| Gold licence shared on an office LAN | Inside the officeOnly on the local network | Remote users, plus the 30-day licence check and connected features |
| Remote access to an office PC | NoFor remote users | Both ends: the office PC must stay on and online all day |
| Tally on Cloud (a Windows server) | NoYour device must reach the server | Your device only. The server is always online, so GST and banking features work whenever you connect |
So the honest answer for Tally on Cloud is no: without internet you can't open your books. In return, there is no office PC to keep switched on and nothing to sync, and the licence check never lapses, because the server is always online. Weighing the remote options against each other? Our comparison of Tally remote access methods covers Tally's own remote access, AnyDesk-style tools and cloud servers, and TallyPrime Cloud Access vs Tally on Cloud covers Tally's hosted service.
If a site regularly loses internet for days at a time, a cloud server alone isn't the right fit there. Tell us about it before you move, and we'll talk through options honestly.
Tally cloud slow? Work through this checklist
When Tally on Cloud feels sluggish, first work out which kind of slow it is. If typed characters appear late, the cause is the network. If a report takes a long time to open while typing feels fine, the work is happening on the server, so tell us and we'll look at its size and load. For a Tally that is slow on an office network, our Tally slow in network guide covers LAN causes. For network lag, try these in order:
- Plug in a cable, or move closer to the router and use its 5 GHz Wi-Fi.
- Switch off any VPN and connect directly. The session is already encrypted.
- Find what's filling the line: video calls, CCTV uploads, phone photo backups, Windows updates or large downloads.
- Pause big uploads during billing hours, because uploads delay everything behind them.
- Try a phone hotspot for ten minutes. If it feels better, the problem is your broadband's route, not the server.
- Lower the session's resolution or use one monitor instead of two, which reduces the screen data RDP has to send.
- Update Windows App or Remote Desktop Connection to the latest version.
- Restart your router, and ask your ISP about line faults if the lag returns every evening.
- Send us the details: the time, your location, the connection type and a ping result. Support 7 days a week, on WhatsApp or by phone.
Moving from a slow office set-up? Our Tally cloud server page explains how we size vCPU, RAM and SSD storage for your users, so reports run on hardware matched to your data.
Frequently asked questions
How much internet speed do I need for Tally on Cloud?
Not much. Tally's TVU FAQ recommends a minimum of 512 Kbps for virtual use, and Microsoft puts active spreadsheet-style Remote Desktop work at about 150–200 Kbps, with an idle session near 0.3 Kbps. Plan roughly 0.5 Mbps for each person working at the same time on one line. A stable 4G or broadband connection is enough; printing long reports briefly needs more.
Is 4G enough for Tally on Cloud?
Usually, yes. Remote Desktop sends screen changes and keystrokes, not your company data, so TallyPrime's text-heavy screens need far less than a working 4G connection normally delivers. What matters on mobile is a steady signal and a short round trip to the server. Weak indoor coverage, crowded towers or a moving vehicle cause the lag people blame on speed, so test from where you actually work.
Why does Tally on Cloud feel slow on a fast connection?
Because responsiveness depends on latency, the round trip from your keyboard to the server and back, not on download speed. RDP guidance treats under about 100 milliseconds as ideal, and Microsoft's planning advice for its own cloud desktops asks for under 150. Wi-Fi interference, VPNs, big uploads on the same line and long network routes all add delay, so try a cable or compare with a phone hotspot.
What happens if my internet disconnects while entering a voucher?
TallyPrime keeps running on the server. Reconnect soon and you usually return to the same screen, often with the half-typed voucher still open. Vouchers you have already accepted are safe, because they are saved on the server, not on your device. For security, disconnected sessions are logged off after a set time, and an unsaved voucher is lost then, so ask us for your server's limit.
Does Tally work without internet?
TallyPrime installed on your own PC works offline for everyday entries, but Tally's licensing FAQ says the computer must connect to the internet at least once every 30 days or the licence turns to Educational mode. GST uploads, e-invoices, e-way bills and Connected Banking always need a connection. Tally on Cloud needs internet to reach the server, so keep a phone hotspot as a backup.
How much mobile data does Tally on Cloud use?
Less than most people expect. Taking Microsoft's figure of 150–200 Kbps for active spreadsheet-style work, a full hour of nonstop screen changes comes to roughly 70–90 MB. Real sessions include long pauses, and an idle session uses only about 0.3 Kbps, so actual use is usually lower. Printing, copying files and very large screens push it up, so check your data usage after the first week.
Sources we checked
All sources were checked on 2026-10-06. If something has changed, tell us and we'll correct it.
- Microsoft Learn: Remote Desktop Protocol bandwidth requirements (bandwidth by scenario, input and heartbeat sizes, printing, minimised windows)
- Microsoft Learn: Network and Remote Desktop client planning (round trip under 150 ms)
- Microsoft Learn: Session Time Limits (disconnected sessions)
- Tally Solutions: Tally Virtual User FAQ (512 Kbps recommendation) and Licensing FAQ (30-day internet check)
- Tally Solutions: Checklist for troubleshooting performance issues (log off rather than disconnect)
- itopia Help Center: Troubleshooting user experience over RDP (latency thresholds)