Tally is slow in network mostly because every client PC reads company data across the LAN, and Gold without TallyPrime Server handles one request at a time. Fix it in this order: one shared data folder on the main PC's SSD, antivirus exclusions for Tally's files, cables with ping under 5 ms, then split old years and add RAM.
Sources: Tally Solutions' performance troubleshooting checklist (updated 18 August 2026) and TallyPrime Server page, checked 6 October 2026.
Why Tally is slow in network, in plain words
Why is TallyPrime slow on the billing desk and quick on the main PC? Because of how Gold shares data. In a typical multi-user office, one PC holds the company data in a shared folder. Every other PC runs its own TallyPrime and opens that folder over the network. Tally's TallyPrime Server FAQ explains that, without TallyPrime Server, the data is shared through Windows file sharing and requests are handled first come, first served. Its performance checklist says the same thing more bluntly: one client's request has to be processed before a response goes to the next.
So when TallyPrime is running slow in network mode, the delay on any client PC comes from three places. Every one of the nine fixes below attacks one of them:
Where the data lives, its disk and memory, antivirus and folder permissions.
If Tally is working slow on the server PC itself (the main PC that holds the data), the network is off the hook. Jump straight to the main-PC fixes: 2, 5 and 4.
Quick diagnosis flow: find your most likely fix
Answer up to five questions. Each answer narrows things down, and the flow ends at the fix most likely to help first. Keep F1 › About open on one PC; it shows the release and where the company data lives.
Is TallyPrime also slow on the PC that holds the company data?
That's the main PC whose folder everyone else opens. If the flow doesn't start, use the table of nine fixes below.
The nine fixes at a glance
| Fix | Cures this symptom | Cost | Effort |
|---|---|---|---|
| 1. One shared data path on the main PC | Slow on clients only, or "data path not found" after a restart | Free | Low |
| 2. Antivirus exclusions | Slow voucher saving everywhere | Free | Low |
| 3. Cable, switch, ping under 5 ms | Slow or freezing on some clients | Cables and a switch | Low to medium |
| 4. Split or archive old years | Slow company loading and long reports | Free | Medium, best at year end |
| 5. SSD, RAM and no sleep | Slow everywhere, including the main PC | An SSD or more RAM | Medium |
| 6. Offline Files off | Laptops slow, stale data, sync conflicts | Free | Low |
| 7. TallyPrime 7.x loading options | Slow opening of companies and reports | Free with active TSS | Low |
| 8. TallyPrime Server | Saves queue at peak times on a healthy network | ₹2,70,000 + GST | High |
| 9. Permissions and workgroup | Slow or erroring on one PC or one login | Free | Low |
Fixes 1–3: data path, antivirus, cable not Wi-Fi
These three cost little or nothing and cure most cases of Tally working slow in a network PC. Do them in this order, and time a few tasks before you start (the before-and-after table below helps).
Fix 1: Keep the data in one shared folder on the main PC's SSD
Every save and every report a client runs is a trip to the data folder and back. The shorter and steadier that trip, the faster Tally feels. The classic cause of a slow Tally network is a data path that adds a detour:
Detours that slow you down
- Company data on a NAS box or an external USB drive. Tally's data FAQ notes that USB 2.0 and 3.0 mismatches on external drives degrade performance.
- Data inside a OneDrive or Google Drive folder, where a sync app touches files while Tally writes them.
- Each client reaching the folder a different way: a mapped drive on one, an IP address on another, the PC name on a third.
- The main PC also being the busiest desk, running browsers, GST portal uploads and Excel all day.
The clean setup
- Data on the main PC's internal SSD, outside Desktop, Documents and any synced folder.
- One share with a simple name, such as
TallyData. - Every client set to the same path, for example
\\MAIN-PC\TallyData. - A static IP on the main PC, so the path never moves.
- Find the current path. On the main PC press F1 › About and note the location of company data.
- Move it if needed. Take a backup first (our Tally data backup guide has the steps), then move the whole data folder to the internal SSD. Copy whole company folders, never single files.
- Share it once from the folder's Properties › Sharing tab.
- Point every client at the same path. In TallyPrime 7.0 and later, set Company Data Path under Alt+Y (Data) › Configuration.
- Fix the address. Tally's server optimisation guide recommends a static IP rather than a dynamic one, so connections don't break when the address changes.
- Check each client with F1 › About. They should all show the same location.
Fix 2: Exclude Tally's files from antivirus scanning
This is the most common reason TallyPrime is slow when saving. Real-time antivirus scans a file every time it changes, and a voucher save changes several. Tally's performance checklist names the culprits: scanning TMessage.tsf and Transmanager.1800 "delays the voucher accepting process". It asks you to add these exclusions on the main PC and every client:
| Add to exclusions | What it is |
|---|---|
| The TallyPrime data folder | Every company's numbered folder. Find the path under F1 › About. |
Tally.exe | The TallyPrime program, in its install folder (by default C:\Program Files\TallyPrime) |
Tallyadmin.exe | A second TallyPrime program in the same install folder |
*.tsf | Tally's message and transaction files, such as TMessage.tsf |
*.1800 | Company data files from TallyPrime 3.0 onwards. Use *.900 for data from older releases |
Then move full scans to after office hours, as the checklist suggests. If backup software runs during the day, Tally's data FAQ says it can lock .tsf files, so exclude them there too.
Exclusions are a trade-off. Keep real-time protection on for everything else, keep Windows patched, and keep at least one backup that ransomware can't reach. Malware itself makes Tally slow, and Tally's FAQ warns that data it corrupts can't be recovered.
Fix 3: Use cables and a switch, and prove it with ping
Tally sets a clear target: ping from each client to the main PC, and back, should always be under 5 ms. It recommends watching it for at least 20 minutes, keeping link speed consistent across the network, and using switches rather than hubs, because a hub copies every packet to every port.
C:\> ping MAIN-PC -t Reply from 192.168.1.10: bytes=32 time<1ms TTL=128 ✓ cable + switch Reply from 192.168.1.10: bytes=32 time=1ms TTL=128 ✓ Reply from 192.168.1.10: bytes=32 time=48ms TTL=128 ✗ spike Request timed out. ✗ dropped # Example output for illustration, not a measurement
- Run the test at a busy hour. Open Command Prompt on a slow client, type
ping MAIN-PC -twith your main PC's name or IP, and leave it for 20 minutes. Ctrl+C stops it and prints a summary. - Read it honestly. Any reply at 5 ms or more, or any "Request timed out", means the network needs work before anything else.
- Test the other direction from the main PC back to the client.
- Compare link speeds in Task Manager › Performance › Ethernet on every PC. One PC showing a lower speed than the rest usually means a bad cable, port or adapter.
- Cable every PC that posts vouchers. Wi-Fi shares airtime with every phone in the office and drops packets when the signal dips; powerline adapters have similar trouble. Wi-Fi is fine for someone who glances at reports, not for the billing desk.
Fixes 4–6: split old years, SSD and RAM, Offline Files off
If the network passes the ping test and Tally is still slow, look at how much work the main PC is being asked to do, and at a Windows feature that quietly gets in the way.
Fix 4: Split or archive old years
Tally's checklist notes that bigger data uses more memory while a company loads, citing a company with 20,000 stock items in 5,000 categories as an example. A company carrying eight years of vouchers makes every client wait for history nobody opens. Splitting gives you a lean company for daily work and keeps the old one intact as an archive.
- Back up the company to a local drive or TallyDrive.
- Verify first: Alt+Y (Data) › Split › Verify Data, and clear any errors it reports.
- Split: Alt+Y › Split › Split Data. Pick the split date and choose From Split Date, Before Split Date or Into Two Companies.
- Archive the original. Tally's split guide says the original company remains as it is. Once you've checked the new one, keep the original in a separate archive folder so nobody opens it by habit.
- Load less. Ask users to shut companies they aren't using with Ctrl+F3, and delete masters nobody uses, which Tally's server guide says improves overall performance.
Splitting is a year-end job, done once the books are final. Our TallyPrime year-end checklist covers the timing.
Fix 5: Give the main PC an SSD, enough RAM and no sleep
Tally's recommended configuration is a 64-bit Windows PC with 4 GB of RAM or more. That's a floor for one user, not a target for the PC serving the whole office. For a LAN of 8 PCs sharing about 200 MB of data, the performance checklist suggests 8 GB on the main PC and 4 GB on each client, and asks for the same RAM on every client so performance is on the same scale. Its hardware page for TallyPrime Server asks for SSD or NVMe storage.
- See what Tally actually uses. In Task Manager › Details, add the "Peak working set (memory)" column and watch TallyPrime at a busy time.
- Watch the disk. If Task Manager › Performance shows the disk pinned near 100% active time whenever someone saves, a hard disk is your bottleneck. An SSD is the cheapest big upgrade.
- Stop power-saving. Tally's server guide asks for the High Performance power plan, sleep set to Never and hard-disk turn-off set to 0 (Never), on the server and the clients.
If the main PC is old enough that you're pricing a replacement, also price the alternative. A Tally cloud server takes the place of the main PC, the UPS behind it and the backup routine that depends on it.
Fix 6: Turn off Windows Offline Files
Windows Offline Files lets a laptop keep a cached copy of a shared folder and sync it later. That's convenient for documents and a bad idea for live accounting data. Tally's data migration and corruption FAQ tells you to disable it to prevent corruption:
- On each client: Control Panel › Sync Center › Manage offline files › Disable offline files, then restart.
- On the main PC's share: folder Properties › Sharing › Advanced Sharing › Caching, and choose "No files or programs from the shared folder are available offline".
If you've already seen damaged companies after a sync conflict or power cut, read our guide to repairing corrupted Tally data before you change anything else.
Fixes 7–9: 7.x loading options, TallyPrime Server, permissions
Fix 7: Check TallyPrime 7.x's loading options
TallyPrime 7.0's release notes promise faster company and report loading through new settings. You'll find them under F1 › Settings › Startup › Enhanced Performance:
| Option | What Tally says it does | Watch out for |
|---|---|---|
| Optimise loading of companies | Companies load much faster | On by default |
| Optimise loading of reports | Faster voucher-based reports such as Day Book and Ledger Vouchers, and faster printing, exporting and sharing | With report-based TDLs, missing columns or wrong values mean you should turn it off |
| Optimise batch processing for data operations | Processes imports, sync and migration in batches | Uses extra memory; turn it off if memory runs short |
From Tally's startup settings help page, updated 10 February 2026.
Here's the twist: the same page says that if you notice any slowdown or issues opening companies or reports, you should set the first two options to No. So don't assume. Time the company opening and your heaviest report with the options on, then off, and keep whichever is faster on your data.
On release 6.2 or older you don't have these options at all. TallyPrime 7.1 is the latest release, and upgrading is free while your TSS is active; our TallyPrime price guide lists TSS renewal costs. Back up before upgrading, because the data may need migrating.
Fix 8: Add TallyPrime Server when saves queue
If the network is clean, the hardware is healthy and the slowdown still appears only when many people save at the same moment, you've hit Gold's design limit: one request at a time over Windows file sharing. TallyPrime Server replaces that with server-based data management, which the TallyPrime Server FAQ says executes multiple processes together.
- Cost: ₹2,70,000 plus GST from Tally, on top of a Gold licence.
- Hardware: 64-bit Windows Server 2012 or later, SSD or NVMe, and separate storage for live data and scheduled backups, per Tally's hardware page.
- What it won't fix: Wi-Fi, a slow disk, antivirus scanning or a huge company. Do fixes 1–6 first.
Before you spend that much, try moving heavy jobs, such as big imports, GST reconciliation and long reports, out of peak billing hours. Then compare the two ways to grow: Tally cloud vs TallyPrime Server sets out the three-year cost of each.
Fix 9: Fix folder permissions and workgroup settings
When only one PC or one Windows login is slow, look at permissions. Tally's checklist asks you to open the data folder's Properties › Security, add Everyone and give Full control, then do the same for Tally.exe. If your IT person would rather not grant access to Everyone, give Full control to the Windows users or group that run TallyPrime instead; what matters is that Tally never trips over a permission check on its own files.
Tally's data FAQ also notes that PCs in different domains can't share data properly, so keep every Tally PC in the same workgroup or domain. Then apply Fix 2's exclusions on that client, and try a different Windows login to see whether the problem follows the user or the PC.
Time it: your own before-and-after check
"It feels faster" doesn't settle anything. Time four everyday tasks with a phone stopwatch before you change anything, then again after each fix. Use the same company and the same PC, at a similar time of day, and take the middle of three tries. Nothing you type here leaves your browser.
Your timings, in seconds
Write the date and the fix beside each set of numbers. That log tells you which change mattered.
Bars show the new time as a share of the old one; shorter is better. Repeat the same four tasks on a trial cloud server to compare like with like.
We don't publish speed figures we haven't measured ourselves, with the method and date beside them. Our editorial policy explains why.
When a cloud server is the real fix
Some offices work through all nine fixes and are still unhappy. Others find the real problem was never the LAN: the people who need Tally simply aren't on it. That's when moving the books to a cloud server stops being an upsell and becomes the straightforward answer. The difference is what has to travel over the wire.
Office LAN (Gold multi-user)
Cloud server (Remote Desktop)
On a Tally cloud server, each person's TallyPrime runs on the same Windows server as the company data. The LAN hop, the Wi-Fi in the data path and Offline Files all disappear from the picture, because the data never leaves the server's own disk. Your device sends keystrokes and receives screen updates, which is why bandwidth matters less than a steady connection; our guide to internet speed for Tally on Cloud covers what you need.
Signs the cloud is the better fix
- People outside the office need the books. Branches, a CA or staff at home. Tally's licensing FAQ says Gold's LAN licensing isn't supported over a LAN created through a VPN, and branch data sync brings its own headaches, covered in Tally data synchronization vs one cloud server.
- Your "server" is an ageing desktop and replacing it means a new PC, a UPS, a backup routine and someone to look after all three.
- You've done fixes 1–6, the network is clean, and people still wait.
- Someone wants TallyPrime on a Mac, iPad or phone, which no office LAN gives you. See Tally on Mac.
What the cloud doesn't fix
- Gold's save queue. Many people saving at the same instant still queue on one server. Very busy teams run TallyPrime Server on the same cloud server; multi-user Tally on Cloud explains how teams and branches are set up.
- An oversized company. Fix 4 still applies. Splitting old years helps on any machine.
- A poor internet connection. Latency to the data centre in Mumbai shapes how the session feels, so test from the places you actually work.
Licences and cost. Remote sessions use Tally Virtual Users, where LAN users don't. Silver includes 1 and Gold includes 10; extra packs cost ₹125 per user a month at Tally's list price, billed annually. Our TVU guide shows how to count them. Hosting with TallyoCloud starts with a private server from ₹799 a month plus GST (see pricing), and we set up the data path and antivirus exclusions from fixes 1 and 2 for you.
The only honest way to know whether it's faster for you is to time it. Run the four tasks from the table above on your office LAN, then on a free 7-day trial server loaded with a copy of your own data. Moving the data over is covered step by step in how to move Tally data to the cloud.
Sources
Settings, menus and figures on this page come from Tally Solutions' help pages for TallyPrime (the current release is 7.1), checked on 6 October 2026:
- Checklist for troubleshooting performance issues of TallyPrime, TallyHelp, updated 18 August 2026
- TallyPrime Server guide for optimised performance, TallyHelp, updated 21 July 2026
- Set up TallyPrime startup options (Enhanced Performance), TallyHelp, updated 10 February 2026
- TallyPrime 7.0 release notes, TallyHelp
- Data migration and data corruption FAQ, TallyHelp, updated 4 February 2026
- Split company data in TallyPrime, TallyHelp, updated 23 March 2026
- Recommended system configuration for TallyPrime and recommended hardware configuration, TallyHelp
- FAQs on TallyPrime Server and the TallyPrime Server product page, Tally Solutions
- Licensing FAQ and Tally Virtual User FAQ, TallyHelp
TallyPrime, TallyPrime Server, TallyDrive and Tally.ERP 9 are trademarks of Tally Solutions Pvt. Ltd. TallyoCloud is an independent hosting provider and is not affiliated with Tally Solutions. Windows is a trademark of the Microsoft group of companies. This guide is general information; ask your IT person before changing antivirus or network settings on business PCs.
Frequently asked questions
Why is Tally slow in network?
On an office network, every client PC reads and writes company data across the LAN through Windows file sharing. In Gold multi-user mode without TallyPrime Server, Tally answers one client's request before it starts the next. Wi-Fi, ping above 5 ms, antivirus scanning the data files, data on a NAS or synced folder, or an underpowered main PC each add delay, and that delay grows with every extra user.
Why is TallyPrime slow even on the main PC that holds the data?
Then the network isn't the cause. The usual suspects are antivirus scanning Tally's data files while vouchers are saved, a hard disk instead of an SSD, too little memory for the size of your company, or many years of history in one company. Check the antivirus exclusions first, then Task Manager's memory and disk graphs, then consider splitting old years into a separate company.
Which antivirus exclusions does Tally recommend?
Tally's performance checklist asks you to add the TallyPrime data folder, Tally.exe, Tallyadmin.exe, *.tsf files and *.1800 data files to the antivirus exclusion list on the main PC and on every client. Use *.900 for data from older releases. Tally says scanning files such as TMessage.tsf and Transmanager.1800 delays voucher saving, so schedule full scans outside business hours.
Is Wi-Fi okay for multi-user Tally?
For someone who opens a report now and then, often yes. For PCs that post vouchers all day, use a network cable. Tally's checklist asks for ping under 5 ms between each client and the main PC, held for at least 20 minutes, with a consistent link speed. Wi-Fi shares airtime with every phone in the office and drops packets when the signal dips, so it often fails that test.
Does TallyPrime 7.x load companies faster?
Release 7.0 added Enhanced Performance options under F1 › Settings › Startup to optimise loading of companies, loading of reports and batch processing. They're on by default. Tally's own help says that if you notice a slowdown or problems opening companies or reports, set the first two to No, so time it both ways on your data. On 6.2 or older, the upgrade is free while TSS is active.
Do I need TallyPrime Server to fix a slow network?
Usually not as a first step. TallyPrime Server costs ₹2,70,000 plus GST, needs a Gold licence and fixes one specific problem: many people saving into the same company at the same moment. It won't fix Wi-Fi, a slow disk or antivirus scanning. Work through the free fixes first and consider it only if month-end saving still queues on a healthy network.
Will moving Tally to the cloud make it faster?
Often, for multi-user offices. On a cloud server, every user's TallyPrime runs on the same machine as the company data, so only screen updates and keystrokes cross the internet. Speed then depends on the server's resources and your latency to the data centre, and Gold still queues saves made at the same instant. Test with a copy of your own data during a free 7-day trial.