Missing Extensions in Google Sheets? Your file may still be Excel

If you opened an Excel workbook in Google Sheets and cannot find Extensions, check the file-format label beside its name. The editor can work with an XLSX without converting it. For a script attached to a native Sheets document, create that document first. The steps below use Sheets in a computer browser.

This is the situation behind a January 2024 r/googlesheets question: someone wanted to add a script to an XLSX and found no Extensions menu. Conversion addresses that obstacle, but it also creates a second file. Before moving ongoing work into it, check what the workbook calculates and which automations it depends on.

Why opening in Sheets does not mean converting

Google’s Office editing documentation says changes made directly to an Office file are saved in its original format. You can collaborate this way. Apps Script, Sheets add-ons and protected ranges require conversion to a Google file.

That makes the next step depend on the work you actually need to do. If a supplier wants three quantities changed and an Excel file returned, retaining the format avoids an unnecessary second working document. If you want a script to process new rows each morning, a native Sheets copy is appropriate. Make a backup before editing either way; Office editing can already change the uploaded original.

Create the copy, then give collaborators one destination

Open the workbook from Drive. If you see a preview, choose to open it with Google Sheets. Select File → Save as Google Sheets. Google’s conversion instructions confirm that this creates a Sheets file while leaving the Excel file in place. Renaming an XLSX is not a conversion.

Open the new spreadsheet and look for Extensions there. Google’s add-on help specifically identifies Office editing as a reason the add-on option may be missing. Installing a random Chrome extension is not the conversion step: a browser extension and the spreadsheet’s Extensions menu are different things.

Give the files distinct names, such as “October orders — original Excel” and “October orders — working sheet.” Send collaborators the working link and tell them when to start using it. Otherwise, one person may update the original workbook while another updates the new spreadsheet, leaving you to reconcile two sets of orders.

Keep the untouched file you received as well, if you need an audit reference. Conversion preserves the Excel file as it exists then; it does not undo edits you already made in Office editing mode.

Test the next calculation, not just the displayed total

Open the Excel original and converted spreadsheet side by side. Compare tab names, the final data row and the totals that matter to the workflow. Then use test copies to change an input. A sheet that displays yesterday’s answer correctly still needs to calculate tomorrow’s answer.

For an order sheet, change one item’s quantity from two to three. Its line total should increase by one unit price, and the overall total should change accordingly. If only the converted copy behaves differently, compare that cell’s formula and references. If neither file updates, investigate the original calculation before blaming conversion.

Google now supports importing Excel tables as Sheets tables, as well as importing pivot tables. Check the specific grouping you use instead of assuming every pivot must be rebuilt. For a sales report, compare one department’s source rows with its subtotal. Matching grand totals do not establish that each department received the right allocation.

External dependencies need their own test. Google lists linked Excel spreadsheets and macros as unsupported Office-editing features. If the workbook pulls prices from another workbook, check how a new price will reach the converted file. Keep the existing Excel refresh process in service until the replacement produces the expected result.

Run these checks before inviting live edits. If colleagues keep working in Excel during the trial, bring over their final changes before switching everyone to Sheets. A clearly agreed handover time is easier to manage than two active versions with different numbers.

Resolve ambiguous dates before changing the whole file

A date such as 03/04 can mean different things to colleagues in different countries. Check the intended date in the original, then display the converted value with an explicit month and year. Changing its appearance does not prove that a date stored as text has become a usable date value.

Under File → Settings, check the spreadsheet’s locale and time zone. Locale affects default date, currency and number formatting for the document, including collaborators. The language of your menus does not establish the spreadsheet’s locale.

For a delivery schedule, compare dates from two different months and try sorting a test copy. If the order follows text rather than chronology, inspect the underlying entries. Repeatedly changing the document-wide locale can introduce new ambiguity without fixing the incorrectly interpreted cells.

Rebuild the VBA task in the converted spreadsheet

An Excel macro does not become executable Apps Script when you save the workbook as Sheets. Inventory what it does: formatting a header, reading another file and producing an output workbook are different migration tasks. Use Extensions → Apps Script in the converted file when you are ready to implement the replacement.

For simple repeated formatting, start with Extensions → Macros → Record macro. Choose absolute references for fixed cells or relative references for work that follows the selected position. Perform the formatting, then name and save the recording. Run it from Extensions → Macros; the first run may request authorization. Test it from a different selected cell to see whether it affects the intended range.

For larger VBA projects, Google offers Macro Converter to Workspace Enterprise Plus and Education Plus users. Its workflow includes compatibility reports and code repairs; it is not an automatic promise that every workbook button will work after conversion.

Test the replacement with more than a successful row. For an automation that appends a summary, try a blank quantity and a repeated run as well. Record whether it skips incomplete input and whether running twice duplicates the output. Run these cases on a small copy before processing live orders.

Set up editable inputs and protected calculations

If colleagues will enter quantities while a maintainer manages the formulas, set that division of work in the converted sheet. Do not assume Excel’s locked cells kept the same protection. Select the formula range, open Data → Protect sheets and ranges, and add the range. Under Set permissions, restrict editing to the people responsible for the formulas. Choosing only a warning would let a colleague dismiss it and overwrite a formula.

A warning may suit a different arrangement where the person preparing a quotation is allowed to enter an exceptional amount. Once you have chosen the intended behavior, have a collaborator try both a quantity cell and a calculation cell. Confirm that quantities remain editable and that changing a formula is either blocked or prompts the agreed warning. The owner’s editing screen does not show what that collaborator is allowed to do.

Range protection does not prevent copying or exporting the contents. If a customer must not see internal costs, prepare a separate document containing only the information they should receive. Hiding a cost tab inside their copy is not a substitute for removing that data.

Reopen the Excel handoff and preserve its date

When an Excel copy is required, use File → Download and choose Microsoft Excel. Reopen the downloaded file in Excel and check key totals, dates and the tabs the recipient will use. If they will edit quantities, try that operation in a test copy too.

Be explicit about automation. Microsoft’s format documentation distinguishes XLSX, which cannot store VBA, from macro-enabled XLSM. Downloading your Sheets file as XLSX does not convert an Apps Script workflow into an Excel macro. A recipient who needs the original VBA process still needs that Excel workflow or a separately implemented replacement.

Before sending, open Sheets’ version history and name the relevant version, for example “October 27 customer handoff.” Editors can later inspect it or make a copy of that earlier version without replacing everyone’s current work.

Tell the recipient whether you expect edits in the shared sheet or a revised Excel attachment back. Their downloaded workbook will not send changes into your working spreadsheet. Assigning someone to incorporate returned changes prevents the next handoff from quietly using an older set of figures.