Skip to content
START WITH THE WORKBOOK YOU HAVE

Excel to app.Imported data. A Google Sheets database.

Turn an Excel workbook into a web app by importing its data into Google Sheets. Upload .xlsx or CSV, describe the workflow, connect Google, then preview and publish; your app uses the imported sheet, while the original local file stays separate.

Google Sheets as your database Code you can inspect
Try the inventory example
START WITH YOUR SPREADSHEETS
Spreadsheets and instructions
Drop your spreadsheets hereExcel (.xlsx) or CSV · Resumable upload to your Google Sheets
Mix files and links · Up to 5 spreadsheets
Add instructions optional

Next: sign in and connect Google. Your starting point is saved. No API key needed.

Your Google Sheets remain the database. AI uses relevant data to build your app. Data & privacy

A FAMILIAR FOUNDATION
Keep business data in Sheets
Review access before sharing
Build and refine with AI

How can I convert an Excel sheet into an app?

  1. Click Browse files and choose an .xlsx workbook or UTF-8 CSV. Old .xls files need to be saved as .xlsx first.
  2. Open Add instructions and describe who will use the app and what they should do. Confirm the data-connection notice, then click Build my app.
  3. Sign in and connect Google when prompted. The upload is converted into Google Sheets in your account, rather than used as a live desktop Excel connection.
  4. Inspect the private preview and generated code in Studio. Check the imported values, calculations, and editing permissions before using real records.
  5. Publish the tested app and share its hosted link. Future data edits belong in the connected Google Sheet or approved app fields.

Questions before you build

Can I turn an Excel calculator into a web app?

Yes, you can import its data and describe the calculator you need. Google converts the workbook into Sheets, so verify important formulas after import and test the generated calculations; macros do not become executable app actions.

Can I update products and prices after building the app?

Yes. Update the connected Google Sheet or approved writable fields in the app. Changes to the original local Excel file do not sync after import, and formula cells remain read-only through the app.

Does this turn my workbook into an iOS app?

It creates a hosted web app that opens in a browser, including on a phone. Native iOS packaging and App Store submission are not included.

Can an imported workbook contain multiple worksheets?

The connection lets you review worksheets and approve the tables and columns your app needs. Check each required tab after Google converts the workbook; importing a file does not guarantee that every layout or cross-sheet calculation is suitable for editing through an app.

Do I need to code the app myself?

No, you can describe your workflow and ask AI to generate and revise the app. Review the private preview and generated code in Studio, and test representative records instead of assuming that a working-looking screen reproduces every workbook rule.

Can I convert my VBA macros into app actions?

This import does not execute or translate VBA macros. The builder accepts .xlsx and CSV; describe the behavior behind a macro separately and test any generated replacement against known inputs and outputs before adopting it.

Prepare an import that preserves the records you need

Start with a copy of the workbook and identify which worksheets hold actual records. A customer list, product catalog, or order table gives the app a clearer structure than a dashboard arranged for printing. Use recognizable headers and inspect duplicate identifiers, blank rows, and mixed values before import. Decide what one row represents instead of combining summaries and individual records in the same table.

The builder accepts .xlsx and UTF-8 CSV. Save an older .xls workbook as .xlsx before selecting it. A CSV carries values from a table; it does not carry workbook formulas, multiple tabs, formatting, or macros. Choose .xlsx when the workbook structure matters, then review the converted tabs rather than assuming every Excel feature survives conversion.

Google converts uploads into Sheets in your account, and the app uses that imported data. Compare a few representative records before building further: a product code with leading zeros, a date, a decimal amount, and a blank optional value. Confirm that these still mean the same thing after import. The inventory app example and sample CSV provide a small four-column reference for a table-shaped input.

Turn a calculation model into a testable app workflow

An Excel calculator contains more than data: it can combine formulas, validation rules, formatting, and macros. Importing the file is not the same as reproducing all of that behavior in a browser. Identify the inputs a person changes, the outputs they rely on, and the rules that connect them. Keep a small set of known input/output examples from the original workbook to compare with the result.

For a quotation workflow, describe product selection, quantity, discount, and the expected total. Explain whether prices come from a table and whether the app should display or calculate the result. Google performs the workbook conversion; formula cells are read-only through the app, and a new row does not automatically copy formulas. VBA macros do not turn into executable app actions.

Test a normal quote, zero quantity, a missing product, and a changed price. If the new app calculates a result itself, compare those outputs with the original model and investigate differences before sharing. If the workbook’s macros, desktop integrations, or exact calculation behavior are essential and cannot be reproduced reliably, keep that workflow in Excel rather than treating conversion as a guaranteed replacement.

Move the team to one source after conversion

After import, the connected Google Sheet is the app’s data source. Editing the old local workbook does not update it. This is the most important handoff to explain to colleagues: continuing to edit both copies creates different versions of the same records, even if both files initially contain identical data. Decide which source the team should maintain before introducing the app into everyday work.

For a small product catalog, choose a few test products and give the app a limited job such as searching products and updating an approved stock field. Make a controlled edit, check the corresponding imported row, and confirm that the original workbook remains unchanged. Then test the permissions for people who should only view records versus people who should edit them.

If your team already maintains the live data in Sheets, use a Google Sheets to app connection instead of exporting and importing a copy. Both paths use a short read cache and require testing of updates; neither promises instant synchronization or database transactions. The goal is a clear operating workflow with one maintained source, not a second interface over an abandoned copy.

Choose a first app that is small enough to verify

A focused record workflow is a useful first conversion: search a customer list, review open orders, or update stock quantities. Define one audience and a few actions before describing the app. For example: “Build a product catalog from this workbook. Search by SKU or product name, display current quantity, and let authorized editors change Quantity. Keep calculated fields read-only.”

Review the imported worksheets and approved columns in Data settings, then test the private preview. Check an existing record, an empty search, and an allowed edit. For a multi-sheet workbook, name each table’s role and how records relate; do not assume that similarly named columns automatically establish the relationship you intend. Review generated behavior before relying on a summary assembled from several tables.

The output is a hosted web app, not a native iOS package, an executable Windows file, or an automatic reproduction of Excel’s interface. If that browser workflow fits, continue with the spreadsheet to app builder and publish after reviewing access. If you need a customer portal with isolated records, offline desktop operation, or guaranteed transaction behavior, evaluate a tool designed for those requirements. Read the data and AI privacy details before importing confidential workbooks.