Does Google Docs show if you copy and paste?
Google Docs never prints the word pasted anywhere, and the record still shows it. Every document keeps a revision log of each edit with a timestamp. A paragraph you type arrives as hundreds of small insertions, and a paragraph you paste arrives in one. Anyone you give edit access to can open that history, and a free extension replays it like a film. The same record is the best evidence you have that the writing is yours.
What the revision history actually keeps
Open any Google Doc, click Last edit at the top right, and a panel of earlier versions opens on the right. Google's own help page for finding what's changed in a file puts one condition on it in bold: "To browse earlier versions of a file, you need permission to edit that file." That single sentence decides most of what follows.
What sits behind the panel is finer than the panel shows. James Somers, who reverse-engineered the format in 2014 to build the replay extension Draftback, described what he found: "every document written in Google Docs since about May 2010 has a revision history that tracks every change, by every user, with timestamps accurate to the microsecond; these histories are available to anyone with 'Edit' permissions". The article he tested it on held 39,154 revisions. The reason the data exists at all is collaboration, not surveillance. To show one person what another is typing in real time, Docs has to record fine-grained edits.
The panel groups those raw edits into readable versions, which you can open with the expand control. Two things the same help page adds are worth knowing before you need them. A named version is protected: "You can create a named version to track your version history and make sure your versions aren't merged", up to 40 per document. And the owner can wipe the record, removing "all versions of your document that have not been explicitly named", with the warning that "deleting version history is permanent and cannot be undone".
On a paid Google Workspace plan there is one more layer. On Business Standard and Plus, Enterprise Standard and Plus, and Education Plus, you can select a passage, right-click and choose Show editors to see who wrote that specific part.
A paste is not labelled, it is shaped
Nothing in Google's documentation describes a paste flag, a clipboard log or an origin field. Version history compares one version with the next and highlights what changed. It records the edit, not the method.
Which is why the answer is yes in practice and no in the way people mean it. Typing produces a long tail of tiny insertions spread across minutes. Pasting produces one insertion of 600 words with a single timestamp, sitting in an otherwise thin stretch of history. Nobody has to be told which is which. The site for Draftback quotes a private-school administrator describing exactly that reading, saying the tool lets them see "whole blocks of text be replaced faster than they could be re-written".
That shape is a fact about the record, not a verdict about you. The same one-step block appears when you paste your own notes from another file, paste a long quotation, restore an earlier version, dictate a paragraph, or write on a phone keyboard that batches its input.
Offline work belongs on that list too. Google's help for using Drive files offline says that when you edit a file offline, "changes are implemented when you're back online" and "you can find edits in the file's version history". What it does not document is how those edits are timestamped once they sync, and we could not find a statement from Google either way. So nobody, in either direction, should build an argument on the clock on a synced block.
Who can open it, by access level
The share dialog decides how much of your writing you are handing over, and most people have never thought about it. Somers put it plainly in that same article, in a parenthesis that has aged well. Everyone he talked to was "surprised, and maybe a little unnerved, to discover that whenever they share a Google Doc with someone, they're also sharing an extremely detailed record of them typing the thing".
| What you gave them | What they can open |
|---|---|
| Viewer | The document as it stands now. No version history. |
| Commenter | The same, plus comments. Still no version history. |
| Editor | The full history, every earlier version, restore, and a copy of any version as its own file. |
| Owner | All of that, plus permanent deletion of every unnamed version. |
| Workspace admin, on a school-owned file | Drive log events, which record view, edit, download, print and copy on supported editions. |
The bottom row is the one students rarely picture. If the document lives in a school or university Google account, an administrator can search Drive log events for it. Google notes that "not all activities in Drive are logged" and that "most Drive audit events are logged only for files owned by users with supported editions", so this is an institutional capability rather than something a module tutor opens on a whim.
There is a smaller mirror of it inside Docs itself. On work and school files, the Activity dashboard shows who has viewed the document, and Google's help page for it says a viewer can switch their own view history off under Tools, then Activity dashboard privacy. On a personal Google account there is nothing to see at all, since "if the file isn't owned by a Google Account through work or school, no one can see the view history".
The replay tools, and what their maker says
Draftback is the one teachers actually use. Its own site describes it as "a Chrome extension that lets you replay the revision history of any Google Doc you can edit", says it has more than 500,000 users, and is direct about who they are: "mostly used by teachers to detect plagiarism and to find out when students are using AI and LLMs like ChatGPT".
Two things it says about itself matter more than the feature list. The first is that it collects nothing. Asked whether it records people as they type, the Draftback site answers: "No, Draftback doesn't record anything. Google Docs itself keeps a record of nearly every minor edit that users make, in order to power its realtime collaboration features." The extension is a reader of data that was already there.
The second is that it refuses to be a detector. Its author, James Somers, writes that one "philosophical choice I remain committed to with Draftback is not 'flagging' things as 'suspicious' or even unusual, but rather just presenting uninterpreted playback, statistics, visualizations, etc., that users can make sense of using their own judgement and experience", adding that he would like to "buck the trend of 'AI detection software' that, in the end, doesn't really work".
That is an unusually honest posture, and it changes what you are dealing with. A replay is not a score. There is no number, no threshold, no percentage to argue about, which is the whole problem with the software kind, covered in what makes a detector flag ordinary writing. There is a person watching how a document was built and drawing a conclusion. That is better in one way and worse in another. It cannot produce a false positive out of statistics, and it also cannot be appealed with a study.
What the history cannot tell anyone
- Where pasted text came from. Inside one document the record is detailed enough to follow a phrase you cut from one paragraph into another, because each character carries its own history. Text arriving from outside arrives with no origin at all.
- What was in the other window. A chatbot, your own notes, a PDF, an essay you wrote last year. The document knows only that characters appeared.
- Who was at the keyboard. It knows the Google account, which is not the same claim.
- Anything about a copy. Make a copy and you get a new file whose history starts when it is created. Download it as a Word file and none of the revision history travels with it.
- Anything the owner deleted. Unnamed versions can be wiped permanently, which is also the single worst move available if a question about your work may be coming.
The same record is what proves the work is yours
Turn the page over and the thing that worries you is the thing that protects you. Most students have nothing to offer when a marker asks how an essay came to exist. Anyone who wrote in one Google Doc from the first note to the final edit has a great deal, and did not have to do anything special to get it.
What reads as genuine is the process, not the polish. Sessions spread across days rather than one long night. A paragraph written, cut and written again. A section moved after the argument changed. Notes at the bottom that get absorbed into the body and disappear. Sources arriving before the claims that lean on them. That pattern is extremely hard to fabricate after the fact and extremely easy to produce by working normally.
It is evidence, not proof, and overselling it is a mistake. A history shows a document being built, which is consistent with writing it yourself and also consistent with typing from a printout. Present it as what it is. The full argument, including what else belongs beside it, is in how to prove you didn't use AI, and if a message has already landed in your inbox, start with what to do when you are accused. If the accusation is coming from a number rather than a person, what a Turnitin AI score actually measures is the other half.
How to keep a history worth showing
Five habits, none of which cost anything.
- Work in one file. Opening a fresh document for the clean version throws the record away at exactly the moment it becomes worth having.
- Name a version at each milestone. Outline done, first draft, after feedback. Named versions are the ones Google will not merge, and 40 is more than any essay needs.
- Explain your own big pastes while you remember them. If you move 800 words of your own notes in at once, say so in a comment or a line at the bottom. The wall of text is the only thing anyone can question, so give it an answer in advance.
- Never delete history while a question is open. It is permanent, it looks exactly like what it would be, and it destroys your own best evidence.
- Keep the sources beside the text. Record where each one came from and the exact line that supports each claim, as you write. That is the part a marker can check in a minute, and it is the failure that causes far more trouble than a detector score, since AI makes up references that look perfect and resolve to nothing.
The handing-in side of this keeps a much thinner record than your editor does, which is worth knowing before you argue from it: see what Canvas logs and what it cannot see. And the version you want to end up with is unglamorous. A draft built in one place, with a history you would be happy to replay, citations that resolve when someone opens them, and every edit in it one you read before you kept it. Our free citation checker takes care of the last check in about a minute.