GridCraft vs Excel: files, workflows and a fair comparison
Compare GridCraft with Excel for one practical task. Documented differences, file limitations and checks for a future hands-on test.
Last updated
Menus and supported features can change. Compare the source-check date below with your current app version.

Is GridCraft a useful option beside Excel? I would decide that around an actual job rather than the resemblance of the interface. For this comparison, the task is to build a budget-versus-spending table.
This is a comparison of public documentation. I have not installed both apps and measured them side by side. There is no verified winner, speed advantage or compatibility score in this article. The table separates what is documented from what still needs testing.
What changes in the workflow?
Repeated edits to a small table are interesting, but an Excel comparison needs separate checks for calculated results, original formulas, recalculation and charts. A workbook can show correct cached values yet fail to update after an edit. CSV also carries a different kind of result from an editable workbook with styles and charts.
| Question | GridCraft | What to check against Excel |
|---|---|---|
| Development stage | alpha / in development | The required behaviour in the actual version used |
| Delivery model | Developer describes free, open-source, local work | Official product/plan terms and your workflow requirements |
| Automation | Documented command/agent-control paths | Manual correction needed after a repeated operation |
| Files and results | Supported routes have the limitations discussed below | Compare results and error cells for identical values and formulas. |
An open-source release lets you inspect the code, but it does not remove time spent learning, checking exports or repairing incompatible files. I have not calculated total cost. Use the linked official baseline page for the relevant regional terms instead of assuming one price applies to everyone.
The file limitation that matters here
The README lists real XLSX fidelity, large workbooks, recalculation and chart depth as areas for improvement. Some XLSB/ODS imports use cached values rather than original formulas. That can make a workbook appear correct on opening while losing the next calculation. Macros, external data and specialised formulas need checks beyond this small exercise.
How I would make the comparison fair
Use the same inputs in both tools: Three budget rows: Food 300/340, Transport 120/100 and Subscriptions 50/50, where each pair is budget/spending.
Keep the output settings, computer, OS and app versions in the record. If one app cannot complete an operation, record where it stopped; do not quietly give only that app an easier input. Separate installation, editing, revision and export time. Errors and manual recovery are part of the workload, even when the final image or document looks good.
| Check | Matched task | Current result |
|---|---|---|
| Calculation | Compare results and error cells for identical values and formulas. | Not hands-on compared |
| Round trip | Inspect formulas, conditional formatting, charts and pivots in the same XLSX. | Not hands-on compared |
| Scale | Measure opening, recalculation and saving for the same large workbook. | Not hands-on compared |
Agree on what counts as finished
A budget table should do more than display a believable total. If spending changes, the differences and chart need to follow it. GridCraft is a spreadsheet app with formulas and workbook editing. I would begin with three rows whose answers we can check ourselves, then save, reopen and change one number. That tests continued calculation rather than just the first screenshot.
Keep an XLSX containing the formulas, not only a picture or cached totals. After reopening, change an input and inspect both its formula result and the aggregate. Check that conditional formatting and the chart still refer to the intended cells. A separate CSV can hold tabular values but should not be mistaken for the full styled, editable workbook.
Producing a delivery file is only one part of completion. Reopening the editable version and making one small change checks whether the next revision remains possible. Keep the first output and the revised one so the difference can be inspected. A source-format round trip also needs a test in the app where the file will actually be received.
Where I would start, and where I would pause
Three rows with independently known answers make a useful first calculation check. They do not establish accuracy of a large workbook, advanced formulas, macros or external-data connections. Opening XLSB/ODS with plausible values is also not proof that its original formula logic survived.
Record the cell inputs, expected formulas and the second calculation after changing spending. For larger comparisons, use identical workbooks and measure opening, recalculation and saving separately. Inspect charts and styles after a round trip, and count errors rather than deciding from the table’s visual neatness.
The review can be updated with a hands-on result once there is a record of the installed version, source files, matched settings and failures as well as successes. For now, these are practical comparison criteria based on the checked documents, not observations from a completed benchmark.
Introduction · Task tutorial · Comparison: documented differences
Sources & further reading
- https://getartcraft.com/apps/gridcraft
- https://github.com/storytold/gridcraft/blob/main/README.md
- https://www.microsoft.com/en-us/microsoft-365/excel
- https://github.com/storytold/gridcraft/blob/84acf6293b1dc1fc09837524e035d674eb4d6741/README.md
- https://github.com/storytold/gridcraft/blob/84acf6293b1dc1fc09837524e035d674eb4d6741/crates/ui-egui/src/ribbon.rs
- https://github.com/storytold/gridcraft/blob/84acf6293b1dc1fc09837524e035d674eb4d6741/docs/formula-input.md