If your writing happens in Gmail, Google Docs, LinkedIn, ChatGPT, or any of the dozen webpage editors a busy day cycles through, the humanizer has to live in the browser, not in a separate tab. The TextSight extension opens as a Chrome side panel beside the page. Highlight a passage, click Humanize selection, and the rewrite comes back with the AI percentage before and after. If the text came from something you were writing in, Replace on page puts it straight back into that field. If it came from something you were only reading, you get Copy instead and nothing is overwritten. Facts, names and numbers stay locked. The panel is the interface; the model is the one that powers app.textsight.ai.
A web humanizer is fine for one paste. It stops being fine when you are cycling between Gmail, Docs, LinkedIn, and a chat window a hundred times a day.
The friction in a paste-and-copy humanizer is not the rewrite itself. It is the tab switch, the manual copy, the visual reorientation to a different app, and the paste back. The extension removes those steps. Select a sentence in Gmail, click the toolbar icon, choose a mode, and the rewrite drops into the compose box. The flow is the same whether you are drafting an email, a LinkedIn post, or a ChatGPT prompt.
Writers who humanize a handful of paragraphs across an afternoon care less about model quality (every humanizer is converging there) and more about how cheap each rewrite is to invoke. The extension makes a single humanization a three-second action: highlight, click, mode, done. Over a 50-rewrite session that is meaningful time saved compared to bouncing into a separate tab each time.
The extension is not a separate product. It uses your existing TextSight account, the same monthly word quota, the same Humanization Score logic, and the same humanizer endpoint as the web app. Sign in once, the extension stays signed in, and your usage from the toolbar counts against the same monthly bucket as a paste-flow rewrite. No second subscription, no extension-only credits, no quota fragmentation.
One rule decides which you get, and it is about the text you selected rather than the name of the app you are in.
Anything you can type into. Gmail compose, reply and forward. The LinkedIn post composer and the messaging panel. The X tweet and reply boxes. ChatGPT, Claude and Gemini prompt boxes. Comment fields, ticket trackers, CRM notes, and ordinary form text boxes. If the selection came out of a field you were editing, the panel offers Replace on page and the rewrite goes straight back into that exact selection.
It refuses rather than guesses. Replace remembers the precise text it rewrote. If that text changed while you were reading the rewrite — you kept typing, the page re-rendered, a draft autosaved — it declines instead of overwriting something it no longer recognises. The rewrite is still there to copy.
Password and payment fields are never touched. They are excluded in code, not by convention, so they are not read and cannot be written.
Articles, posts and transcripts. A Substack piece, somebody else's LinkedIn post, a ChatGPT answer in the thread rather than in the box, a news article. There is no field to write back into, so the panel gives you Copy and you paste it where you want it. Nothing on the page is modified.
Editors that keep their selection to themselves. Editors differ in how much they hand to an extension, and a few custom ones expose less than a plain text box does. When the selection does not come through cleanly, you get Copy rather than a silent half-write. There is no paste box in the panel to fall back into, so if neither route works for a particular document, the web app is the honest answer for that one.
Either way it is the same rewrite. Replace and Copy differ in where the text lands, not in what the model did to it.
No extension-only tier, no extension-only credits. Your TextSight account quota applies. Yearly billing saves 25% on every paid tier.
Billed $89.88/year — Save $30
Billed $179.88/year — Save $60
Billed $359.88/year — Save $120
Yearly billing saves 25%. View full pricing →
A standard Chrome extension install. About 30 seconds end to end. No build flags, no developer mode, no unpacked-extension warnings.
Open TextSight: AI Detector & Humanizer on the Chrome Web Store and click Add to Chrome. Chrome shows its permission prompt first. TextSight's content script is declared on all sites, so the prompt is the broad one — read and change your data on the sites you visit. What the code does with it is narrower: it listens, it remembers what you currently have selected, and it sends nothing anywhere until you click a button in the panel. Confirm and the extension installs in a few seconds.
Click the puzzle-piece icon in the Chrome toolbar to open the extension menu. Find TextSight in the list and click the pin icon next to it. Pinning keeps the extension icon visible in the toolbar so you can click it without opening the puzzle-piece menu every time. Most users want this on; the extension still works unpinned but the trigger is one extra click.
Click the TextSight icon and sign in with the same email you use on app.textsight.ai. The extension stores an authentication token locally and stays signed in until you sign out manually or the token expires (typically 30 days). One sign-in per browser profile covers every site you use the extension on. You can also skip this step and try it without an account first.
Open Gmail, LinkedIn, ChatGPT, Substack, or any editor on the web and highlight the sentence or paragraph. Click the TextSight icon and the side panel opens beside the page, showing the opening words of what you selected so you can see it has the right passage. The extension does not act on its own: it only ever sees text you hand it from the panel or the right-click menu.
Click Humanize selection — the button carries the word count — or right-click and choose Humanize with TextSight. There is no mode to pick. The rewrite comes back with the AI percentage before and after, and then either Replace on page, if the text came from a field you were editing, or Copy if it did not. Try again runs the same passage through once more if the first rewrite is not the one.
There is no mode toggle and nothing to configure. Every rewrite returns the same things.
Two pills at the top of the result: how much of the original read as AI, and how much of the rewrite does. It is the same measurement the detector uses, so the number means the same thing it means everywhere else in TextSight — not a score the rewriter marked itself on.
The complete rewritten passage with its word count, not a diff or a preview you have to expand. Facts, names and numbers are held in place; the thing being changed is the rhythm and phrasing that made it read as generated.
Replace on page when the text came from a field you were editing, Copy when it did not, and Try again for a second pass over the same passage. Nothing on the page changes until you choose.
Under the panel, the rewriter words you have left against your plan's allowance and the date it refills. When an allowance is a one-time pool rather than a monthly one, the panel says so instead of drawing a bar that implies it comes back.
You do not have to start on the humanizer tab. Run a detector scan and every flagged sentence carries its own Rewrite button, with a Rewrite all underneath for the set — which rewrites only the flagged sentences, so your allowance is not spent on lines that already read as human.
Browser extensions with broad permissions are a real category of risk. This is the honest list of what TextSight requests, what it uses, and what it ignores.
The extension does not read pages passively. It does not scan form fields, email bodies, or chat history in the background. The only text that ever leaves your browser is text you handed it by clicking Humanize selection or the right-click item. Close the panel without clicking either and nothing leaves the device. Password fields and payment fields are excluded in the code itself and are never read, whatever is selected.
The extension does not inject tracking pixels, third-party analytics scripts, or fingerprinting code into sites you visit. The only outbound network call the extension makes is to the TextSight humanizer endpoint on api.textsight.ai when you trigger a humanize action. That call carries the text you submitted and your authentication token; nothing else.
The extension is governed by the privacy policy at www.textsight.ai/privacy.html. Text submitted through the extension is processed for the rewrite, billed against your monthly word quota, and not retained beyond the standard logging window applied to web app submissions. Sign-out clears the authentication token and the preferences cached on your machine.
The main humanizer landing page covering modes, Humanization Score, and the web-app paste flow.
Open humanizer →REST endpoint for the same humanizer the extension calls. Same model, scriptable from any language.
Read the API page →Umbrella humanizer guide covering source models, mode selection, and detector behaviour.
Open the guide →Full tier breakdown for Free, Starter, Pro, and Business. Annual billing saves 25%.
See pricing →Same humanizer and the same scoring as the web app, in a side panel beside whatever you are writing. Select a passage inside Gmail, LinkedIn, ChatGPT or any text box, and the rewrite goes back where it came from. Install in 30 seconds.
How TextSight works for other regions and setups.