How to dictate without installing an extension on a borrowed computer

On a borrowed computer, an extension install is usually blocked at one of two levels, and the block tells you what remains available. Guest mode, which Chrome uses on unfamiliar machines, keeps the session temporary and discards everything afterwards, and it forbids most extensions by design, since a guest is not a profile with a stable identity. Managed devices, such as school and library computers, go further through policy: the administrator whitelists or blacklists entire categories, and extension installation is simply unavailable to you, with the option grayed out or hidden entirely. In both cases the block is not a defect you can configure around, and any attempt to bypass it is both futile and a violation of the machine's rules, so the real work is finding what genuine dictation paths the browser still offers, and the shortest of them is to dictate without installing an extension.

The key realization is that the block is about extension installation, not about speech input, which is exactly why you can still dictate without installing an extension at all. The remainder of Chrome's capabilities stay open: a guest or managed profile can still type, paste, use web apps, and run the site features that do not require an installed tool, and within that envelope there is more than enough to write a dictation workflow. The only truly lost capability is the always-listening hotkey, the background key that captures your voice anywhere, and every workable no-install workflow compensates by moving the capture step to a surface you control, such as a dedicated tab or your own phone. List the lost and the kept once, and the problem becomes a design question rather than a dead end.

Frame your posture for the session honestly: you are a guest, and the machine is not yours to modify. That is not a restriction on your work, only on your tooling, and it is exactly the situation that taught a whole generation of students the scratchpad habit, write in one place, move to another. The methods in this guide all share that shape, they work with a browser you cannot change and a phone you can, and they produce the same words you would have dictated, just through a slightly different doorway. Before the session begins, agree with yourself which machine is which, since mixing the roles is the only way the no-install setup genuinely fails: one device holds your voice, the other holds the text, and keeping them straight is the price of the workaround.

Chrome includes a native speech input feature that requires no extension, and it is the most direct no-install answer. Find it by right-clicking inside a plain text field, such as a web form or a basic editor, and choosing the dictate or voice option from the context menu, or by looking for the microphone icon inside the field itself on supported pages. A small listening dialog appears, you speak, and the browser inserts recognized text using its own system-level speech recognition, which on most platforms is the speech service built into the operating system. The limitation of this path is surface: it appears in ordinary text boxes and some platform editors, but not in the rich editors of every web app, and not in a page that focuses on its own widgets.

Native speech works best when your target is genuinely a plain field: a search box, a short form answer, a note-taking page, a chat input that uses a standard textarea, and it is least reliable in the apps that render their own custom editors, which is the same pattern the focus lessons of this series predicted for any tool. Treat the free feature as the first-tier path: try it on the current field, and if no dictation option appears, move to the next method rather than forcing it, since the option is either there or not, and no amount of searching changes a missing context menu entry. For quick answers between classes or between meetings, native speech is often faster than any other route, because it costs zero setup on a machine you will leave by five.

Use the native tool with the habits you already know: click into the field first, watch the listening indicator before you speak, and read back the inserted sentence, since the same prose-tuned punctuation behavior of every speech engine applies to the built-in one. If the recognition language is wrong for you, the system speech settings, not the browser, are where the language choice lives, and a quick switch there improves accuracy dramatically for non-native accents. It is humble technology and it is already on the machine, which is precisely its value on a borrowed computer that will not let you add a thing.

The phone bridge is the strongest no-install method, and the name describes the architecture: your phone is the dictation device, the shared computer is the typing surface, and your fingers are the connection. Dictate the text into a note on your own phone, where the phone's speech recognition is already installed and tuned to your voice, and where your products and names are already in its vocabulary, then send the text to the shared machine in whatever way the environment allows, a cloud note, an email to yourself, a quick messaging channel that is open in the browser. Once the text appears in the browser, copy and paste it into the field you are working on, and paste has no installation requirement at all, which is the whole basis of the method.

The bridge per session is deliberately simple. On the phone, dictate directly into your notes app or a dedicated message to yourself, review while the words are fresh, and correct any mis-hearings right there instead of after the transfer, since mobile editors make editing easy and a clean note means a clean paste. On the computer, confirm the note arrives, select all, copy, click the target field, and paste, then run the normal read-through before sending. The only real cost is the transfer step, and for most people the dictation savings vastly outweigh the seconds of copy and paste, particularly for the long first drafts where voice beats keyboard by a wide margin.

Version this workflow to your surroundings. When the machine has a browser open to a note service, dictate into that service's mobile app and the transfer is automatic; when only a messaging app is available, use a channel to yourself; when nothing is open, email is the universal fallback, since every web mail client renders in a borrowed browser. The phone bridge also carries the phrasing habits of your own dictionary, because phone keyboards learn your corrections over time, which makes it a better personal transcript than a bare room mic would be. Between native speech for quick notes and the bridge for serious drafting, a borrowed computer can host a fully voiced workflow.

A guest session discards everything when it closes, so the discipline of the throwaway session is to keep the work in a place that is not the session. The rule is simple: anything you want to keep must live outside the machine, in an account you own, a cloud folder, a note service, or a message to yourself, and nothing of value should exist only in the borrowed browser's memory. Before you start, open the destination, the note service or the draft document you will write into; write there, or dictate and copy there in small steps rather than at the end, since a machine that locks up mid-session costs you one paragraph instead of the whole draft. The workplace habit is the same as the platform habit: remember where the work lives, and choose that location first.

Your vocabulary is the second thing worth preserving, and it survives best in two places. The short term belongs in the phone, since your phone's dictionary already knows your terms, and one phone covers every borrowed machine you will ever use. The long term belongs in a simple list, a note or spreadsheet of the names and jargon you use, so that when you sit at a machine with your own setup, the list is one paste away from a vocabulary import. Practice the preservation ritual once in a real session, draft, copy, verify that the destination has the text, then continue, and the two-minute check will save you from the worst outcome, the empty closing of a window full of undocumented work.

Name your session artifacts from the moment they exist. Title the note with the date and the task, so when you return to it later, the recovery is obvious, and add the destination check to the session close, confirming that each item you meant to keep has a home outside the browser before you close the guest window. These habits are invisible in a working session and decisive in a losing one, and they are the reason experienced users treat throwaway machines as a place where work happens rather than somewhere effort goes to be forgotten. Keep the vocabulary list in the same note as the drafts, because a single artifact that contains both the words and the work is the cheapest thing to export off a guest machine, and one file is far easier to remember than two.

Treat the borrowed session as a bridge, not a ceiling, and design your upgrade path in advance. The path has three steps and each one is a small decision: what you dictated, where you kept the text, and what you will do with it at your own machine. When you return to an environment where you can install, the first task is not to redo the work but to collect it, opening the notes you kept and moving the drafted text into your real projects. The three numbers worth remembering are how many drafts you carried, how much time the phone bridge saved, and which terms survived the transfer, because they tell you at a glance which half of the borrowed workflow is worth keeping permanently.

The second step is vocabulary: import the list you built on the phone into your own dictation tool, and the names you taught your phone transfer in minutes, giving you the same accuracy you grew used to without rebuilding anything. Most dictation tools accept a plain text list of custom terms, so the phone list you kept as one word per line imports directly, and a two-minute review restores the month of corrections in one pass. The third step is habit: decide which patterns worked for you, whether the phone bridge felt natural enough to keep even with an extension installed, or whether the hotkey is the part you missed most, and let the decision shape your own setup. Schedule the consolidation within a day of returning, while the memory of which note held what is still fresh, because a week later the session becomes a pile of unlabeled text.

The upgrade is also a data lesson in reverse. On your own machine, mirror the preservation habits you learned on the borrowed one: keep drafts in cloud notes, keep a vocabulary list, and keep the habit of asking where the work lives. Many users discover that the throwaway-session discipline makes their own habits better, since the borrowed machine taught them to name their threads and save their material, and those habits survive the return to a machine that keeps sessions forever. The borrowed weeks are not lost time; they are the field test that showed you which workflow you actually want.

Finish the path with a small ceremony of consolidation. In one sitting, collect the drafts, merge the vocabulary, and delete the throwaway copies, so the borrowed session becomes a chapter rather than a lingering reminder. When you are done, you have everything you need: the words you worked on, the terms you taught, and a sense of the workflow that fits you, all carried from a machine that would not let you install anything. The no-install fallback was never a downgrade; it was the rehearsal for a setup that could finally be yours. If the consolidation reveals that the phone bridge turned into your daily driver, keep it: the goal was never to return to a single tool, it was to find the combination that produces clean text on whatever machine you are handed that day.