Key takeaway
Browser-local tools process files in your tab; upload suites send bytes to someone else’s servers.
Choose based on sensitivity, features and trust — not vibes alone.
What it means
Local: Canvas/WebAssembly/pdf-lib style processing on-device.
Upload: convenient deep features, accounts, and third-party handling.
TCB Tools labels browser-local jobs honestly and shows limits.
When you would use it
Client drafts, unpublished creatives, internal PDFs → prefer local when features suffice.
Heavy OCR or specialized codecs may still need hosted tools — go in eyes-open.
How to use the tool
Use the matching TCB Tools page and work top to bottom:
- Open a file tool such as Image Compressor or PDF Merger.
- Read limits on the page.
- Run a non-sensitive sample.
- Check Privacy proof where offered.
- Compare with an upload vendor only if needed.
No account is required. Results update as you type.
How to compare + examples
Decision sketch: if file is confidential and the job is compress/merge/split/resize, local usually wins.
If you need a rare filter only a cloud API offers, use a vetted vendor and minimize data.
How to read the result
Local is not magic: huge files can strain memory.
Upload is not evil: it is a trust and contract decision.
Read both privacy policies.
Common mistakes
- Uploading secrets to random free sites. Prefer local/vetted.
- Assuming local means infinite size. Respect caps.
- No audit trail when required. Use approved enterprise tools.
- Ignoring malware scanning policies. Follow company rules.
Related ideas
See Compare page and file tool guides.
Teach contractors your default path.
Keep a short data-handling note for clients.
If you are new, read once for the story, then again for the clicks you will make.
Write inputs down before changing live budgets or deleting files — calm beats guesswork.
Note the date range, currency or filename so teammates can reproduce the result.
Interactive math and many file jobs run in your browser here; treat outputs as planning aids, not certified professional advice.
When a result looks too good, recheck definitions: units, filters and windows hide surprises.
Practice with example numbers first, then replace them with trusted exports.
Small disagreements between systems are often rounding or filters — investigate before panicking.
Consistent naming, windows and currencies beat clever one-off spreadsheets.
Operators who revisit browser-local tools weekly catch drift earlier than teams who only look after emergencies.
Teach one teammate how you measure browser-local tools; shared definitions prevent quiet disagreement.
Bookmark the guide and the tool together so beginners always have both the why and the workspace.
When unsure about browser-local tools, reduce scope: one campaign, one file, one list — prove the method, then scale.
Screenshots of inputs beside outputs speed audits when someone questions browser-local tools.
If leadership wants only a headline, still keep working notes for browser-local tools in your own folder.
Seasonality and promotions change browser-local tools; annotate the calendar when comparing periods.
Automation helps, but a human still owns success criteria for browser-local tools.
Revisit assumptions about browser-local tools after tool, tracking or pricing changes.
A short checklist for browser-local tools beats relying on memory during busy weeks.
Teach contractors your default path.
Keep a short data-handling note for clients.
If you are new, read once for the story, then again for the clicks you will make.
Write inputs down before changing live budgets or deleting files — calm beats guesswork.
Note the date range, currency or filename so teammates can reproduce the result.
Interactive math and many file jobs run in your browser here; treat outputs as planning aids, not certified professional advice.
When a result looks too good, recheck definitions: units, filters and windows hide surprises.
Practice with example numbers first, then replace them with trusted exports.
Small disagreements between systems are often rounding or filters — investigate before panicking.
Consistent naming, windows and currencies beat clever one-off spreadsheets.
Operators who revisit browser-local tools weekly catch drift earlier than teams who only look after emergencies.
Teach one teammate how you measure browser-local tools; shared definitions prevent quiet disagreement.
Bookmark the guide and the tool together so beginners always have both the why and the workspace.
When unsure about browser-local tools, reduce scope: one campaign, one file, one list — prove the method, then scale.
Screenshots of inputs beside outputs speed audits when someone questions browser-local tools.
If leadership wants only a headline, still keep working notes for browser-local tools in your own folder.
Seasonality and promotions change browser-local tools; annotate the calendar when comparing periods.
Automation helps, but a human still owns success criteria for browser-local tools.
Revisit assumptions about browser-local tools after tool, tracking or pricing changes.
A short checklist for browser-local tools beats relying on memory during busy weeks.
Teach contractors your default path.
Keep a short data-handling note for clients.
If you are new, read once for the story, then again for the clicks you will make.
Write inputs down before changing live budgets or deleting files — calm beats guesswork.
Note the date range, currency or filename so teammates can reproduce the result.
Interactive math and many file jobs run in your browser here; treat outputs as planning aids, not certified professional advice.
When a result looks too good, recheck definitions: units, filters and windows hide surprises.
Practice with example numbers first, then replace them with trusted exports.
Small disagreements between systems are often rounding or filters — investigate before panicking.
Consistent naming, windows and currencies beat clever one-off spreadsheets.
Operators who revisit browser-local tools weekly catch drift earlier than teams who only look after emergencies.
Teach one teammate how you measure browser-local tools; shared definitions prevent quiet disagreement.
Bookmark the guide and the tool together so beginners always have both the why and the workspace.
When unsure about browser-local tools, reduce scope: one campaign, one file, one list — prove the method, then scale.
Screenshots of inputs beside outputs speed audits when someone questions browser-local tools.
If leadership wants only a headline, still keep working notes for browser-local tools in your own folder.
Seasonality and promotions change browser-local tools; annotate the calendar when comparing periods.
Automation helps, but a human still owns success criteria for browser-local tools.
Revisit assumptions about browser-local tools after tool, tracking or pricing changes.
A short checklist for browser-local tools beats relying on memory during busy weeks.
Try the tools
Try Image Compressor or PDF Merger, and read Compare.
