Google Drive has begun adding timestamped comments to videos in its web player, giving reviewers a way to pin feedback to the exact moment on screen rather than writing “around 02:14” in an email, chat thread, or separate document. According to Neowin’s August 4 report, a reviewer moves the playback slider to a moment in the video, opens the comment control, and posts a note; the resulting marker on the timeline can be selected to jump back to the associated frame. For teams that already pass screen recordings, training clips, product demos, and Google Meet recordings through Drive, this is a meaningful workflow upgrade. The practical benefit is not that Drive has gained comments — it has offered ordinary file-level comments for years — but that comments now carry location data that the player itself can act on.
There is an important qualification for administrators and production teams: Google has not yet published the usual rollout record for this feature. As of August 5, the public Google Workspace Updates index does not show a dedicated announcement with release-track dates, supported editions, regional scope, supported video formats, or an administrator control. Neowin is currently the only outlet located reporting the feature’s mechanics and availability.
That does not negate the rollout, but it does mean organizations should avoid treating it as a documented, universally deployed Drive capability until Google fills in those details.

Laptop and smartphone display a collaborative video presentation with charts, comments, and remote participants.A useful review feature, delivered inside a storage product​

Timestamped notes solve a routine and expensive coordination problem. A reviewer watching a 45-minute meeting recording can attach “replace the customer name on this slide” to the exact second it appears, rather than forcing the editor to hunt through the recording. A support lead can mark the point where a reproduction video diverges from expected behavior. A training owner can identify the precise segment that needs to be re-recorded.
The reported workflow is deliberately simple: open a video in Google Drive on the web, scrub to the desired point, select the comment button, and post feedback. Timeline markers represent the discussion locations; selecting one sends playback to the marker and surfaces its comment.
That puts Drive closer to the review mechanics offered by specialist tools such as Frame.io, Vimeo Review, and Dropbox Replay. Those products still offer broader production controls, including frame annotations, approval states, comparison workflows, and purpose-built review dashboards. Google’s addition addresses the most basic missing layer: associating a normal Drive conversation with a place in a video.
The feature also closes a long-standing gap in Google’s own collaboration model. A 2019 Google Drive Community request described users being forced to use Dropbox or paid Vimeo plans because Drive comments could not be tied to video timecodes. In a separate 2022 Google Meet Community discussion, a Google product expert advised users to add conventional comments that manually listed timestamps because video bookmarks were unavailable. The new behavior, as described by Neowin, finally eliminates that workaround.

Mobile users will see the discussion, but not the video marker workflow​

Neowin reports that timestamped notes will appear as ordinary file-level comments when the video is opened through Google Drive for Android or iOS. That distinction deserves more attention than it has received.
A comment that points to a moment in a video is useful only when a reviewer can immediately confirm the moment being discussed. If mobile clients expose the conversation as a standard comment thread without the interactive timeline marker, a user receiving feedback on a phone has the note but may still need to locate the referenced scene manually. Google has not publicly clarified whether selecting a timestamped comment in its mobile apps jumps playback to the proper position, whether markers appear in the mobile scrubber, or whether users can create timestamped notes from mobile.
For Windows users, that makes the desktop browser the safe operational path for now. Teams should not train reviewers to rely on mobile capture or mobile approval until the behavior has been verified in their own tenant. The reported launch is specifically for Drive on the web, and Google’s recent product updates often arrive with different capabilities and timing across web, Android, and iOS.
This is also relevant for external review. A client may have permission to comment on a shared Drive file yet open it in the Drive app, a mobile browser, or a managed device with a different account. The comments may remain visible, but the efficient click marker, inspect frame, reply loop is not currently documented outside the web experience.

Drive’s video tools are becoming more capable, but they remain fragmented​

Google has been steadily expanding what a Drive-hosted video can do. In February 2025, Google added searchable video transcripts for videos with captions, allowing users to search spoken text and jump to a matching part of a recording. In May 2025, it extended Gemini in Drive so eligible paid Workspace and Google AI customers could request summaries and ask questions about a video, including prompts to identify action items.
Those features solve different problems. Transcripts help find what was said. Gemini helps summarize what happened. Timestamped comments let people state what should change or what needs attention. Together, they can turn a long recording from a passive file into something closer to a reviewable work item.
But the features do not share the same availability model. Google’s video transcript feature is available to Workspace customers, Workspace Individual subscribers, and personal Google accounts, provided the video has captions. Gemini video analysis has been tied to eligible plans and requires the relevant Drive and smart-feature settings. The timestamped-comment rollout has no published availability table at all.
That gap is more than paperwork. IT teams cannot yet answer basic deployment questions with confidence:
  • Whether personal Google accounts and Workspace Individual subscribers receive the feature alongside business tenants.
  • Whether it is available in Shared Drives, externally shared files, and visitor-sharing scenarios.
  • Whether existing comments can be converted into timestamped markers.
  • Whether the marker and timecode are exposed through the Google Drive API, Vault, eDiscovery exports, or audit logs.
  • Whether a timestamped thread remains correctly positioned if the owner uploads a replacement video version.
The API question is particularly relevant to WindowsForum’s administrator audience. Google’s Drive API supports an anchor field for comments, but Google’s own developer documentation says an app-defined anchor is saved and returned while Workspace editor applications treat it as unanchored. That documentation does not establish how Drive’s new native video markers are represented, nor whether third-party workflows can read them. Until Google documents the implementation, developers should not assume a standard Drive comment export includes usable video timecodes.

The ransomware context needs one correction​

Neowin’s report also points to Google Drive for desktop’s ransomware detection and mass-restoration features. Those are real and substantially more documented than timestamped video notes, but the timing and recovery description need tightening.
Google announced general availability for ransomware detection and file restoration on March 30, 2026. Google says Drive for desktop pauses syncing when it detects ransomware encryption; detection alerts require Drive for desktop version 114 or later, although sync pausing can still occur on older versions. The feature is aimed at stopping encrypted local changes from being propagated through cloud synchronization after an endpoint has been compromised.
The restoration component is available more broadly than detection itself. Google’s published availability says bulk file restoration is available to all Workspace customers, Workspace Individual subscribers, and personal Google accounts. Ransomware detection is restricted to specified Workspace editions, including Business Standard and Plus, Enterprise Starter through Plus, Education Standard and Plus, and Frontline Standard and Plus.
Google’s Drive Help documentation says the Restore file versions tool retains the last 25 days of revisions. That is not the same guarantee as restoring files “up to 25 days prior to the attack point.” Recovery depends on when the encrypted changes were created and synced, whether the relevant files still have prior revisions, and selecting an appropriate restoration point. Google also warns that the bulk tool restores the chosen earlier versions across the selected set rather than letting users pick individual files, and it does not cover Google-native Docs or Slides files because ransomware cannot encrypt their cloud-native contents in the same way.
For Windows admins, the practical sequence remains familiar: isolate and remediate the infected PC first, confirm the last clean point, then restore Drive file versions. A synchronized cloud folder is not a backup strategy merely because it has version history.

Treat the new markers as collaboration metadata, not formal approval​

Timestamped comments will reduce ambiguous revision requests immediately, especially for teams whose current process is “send an MP4 through Drive, then collect notes in email.” They are less likely to replace a dedicated review platform where client sign-off, visual markup, media version comparison, and immutable approval records are contractual requirements.
The absence of a published Google rollout notice leaves one more operational concern: retention and governance. Comments on Drive files can be part of collaboration history, but Google has not said whether the timestamp itself is retained as first-class metadata in exports or whether the visual marker is only a web-player rendering. Organizations subject to records retention, litigation holds, or regulated review processes should test that distinction before replacing established approval workflows.
For everyone else, the immediate action is straightforward: open a noncritical Drive-hosted video in a desktop browser, post a timestamped note, then test it with the same mix of Windows browsers, Android devices, iPhones, internal users, and external collaborators that the organization actually supports. Google Drive now appears to have the review feature teams have requested for years; the remaining work is finding out exactly where — and for whom — it is live.

References​

  1. Primary source: Neowin
    Published: 2026-08-04T13:48:01+00:00
  2. Related coverage: support.google.com
  3. Related coverage: zoho.com
  4. Related coverage: support.google.com
  5. Related coverage: services.google.com
  6. Related coverage: services.google.com
  7. Related coverage: techradar.com
  8. Related coverage: androidcentral.com
  9. Related coverage: techradar.com
  10. Related coverage: androidcentral.com
  11. Related coverage: workspaceupdates.googleblog.com
  12. Related coverage: chromewebstore.google.com
  13. Related coverage: docs.google.com
  14. Related coverage: developers.google.com
  15. Related coverage: androidauthority.com
  16. Related coverage: workspaceupdates.googleblog.com
  17. Related coverage: blog.google
  18. Related coverage: blog.google
  19. Related coverage: drive.googleblog.com
  20. Related coverage: developers.google.com
  21. Related coverage: androidauthority.com
  22. Related coverage: feedtracks.com
  23. Related coverage: notetracks.com
  24. Related coverage: knowledge.workspace.google.com
  25. Related coverage: knowledge.workspace.google.com
  26. Related coverage: help.asana.com
  27. Related coverage: googblogs.com
  28. Related coverage: assets.noviams.com
  29. Related coverage: fan.gov