The short answer is that Google Meet doesn't keep a traditional history file you can browse
Unlike some chat platforms that store a searchable log of every call, Google Meet stores meeting metadata in a few different places depending on what exactly you're looking for. If you're trying to track attendance, check when a meeting happened, or find recordings, the process varies significantly between a regular consumer Gmail account and a Google Workspace environment. Most people asking this question are Workspace admins or IT staff who need to pull records, and a lot of them run into the same wall on day one. You need admin-level access to your Google Workspace domain. The free version of Meet does not provide any centralized meeting logs, period. If you're on the Business Starter tier or above, you have access to the Admin Console and the Security Center, both of which offer some reporting functionality. For individual users without admin privileges, your options are extremely limited to whatever the meeting organizer made available—screen recordings, chat exports, or calendar invites. There's no backdoor for regular users to pull historical meeting data from the platform itself. I spent about three weeks dealing with a compliance audit last year where we needed to reconstruct attendance for every company-wide meeting over a six-month period. The first thing I learned was that Google Meet's built-in attendance report only captures participants for a single meeting at a time. You can export a CSV from any individual session, but there's no bulk export feature for multiple meetings across multiple dates. That meant pulling each one manually, which took roughly forty-five minutes across about eighty scheduled meetings. It was tedious but straightforward once I stopped looking for a feature that doesn't exist.
Where Meeting Data Actually Lives
Meeting logs in Google Workspace are split across several systems and each one gives you a different slice of information. The Admin Console Audit Logs show you that a meeting was created, who created it, and roughly when it happened. The Security Center provides more detail on sign-ins and user activity but isn't designed for meeting-level reporting. And if your organization has a subscription to Google Vault as part of a higher Workspace tier, you get eDiscovery and hold capabilities that can search across Meet recordings and chat transcripts. Sign into the Admin Console at admin.google.com with your super admin credentials. Navigate to Reporting and then click on Audit. From there, select the Google Workspace section and look for the Meet-related audit entries. You can filter by date range, user, and activity type. The default retention window for audit logs in Workspace is typically 180 days for most editions and up to 1 year for Business Plus or Enterprise tiers. If your compliance requirements go beyond that, you need to set up retention rules through Google Vault before those logs expire, because Google doesn't store them indefinitely by default. The audit logs will tell you things like who started a recording, who joined a meeting, and when a meeting ended. They won't give you the content of conversations unless recordings were enabled and saved to Drive. One thing the Admin Console doesn't make obvious is that meeting participation data is spotty. If someone joined via dial-in with a phone number instead of through the Google Meet interface, their attendance often doesn't appear in the reports at all. I found this out the hard way when our finance team complained that half their attendees were missing from the records. The workaround was cross-referencing the Meet attendance CSVs against the calendar event invitations to estimate who should have been there versus who Google actually logged.
Meeting Recordings and Chat Transcripts
If your organization has enabled cloud recording, those recordings are saved to the Google Drive of the person who started them or to a shared folder depending on your admin settings. You can search Drive for files created during a specific time range, but there's no native Meet dashboard that aggregates all recordings in one place. The Security and Compliance Center in Google Vault is the closest thing to a centralized repository, and it requires a Vault license on top of your Workspace subscription. Meet chat transcripts are handled differently. Chat messages from a meeting are stored in the Google Chat activity for each participant. If Vault is enabled, those messages are preserved and searchable through the Vault eDiscovery tool. Without Vault, there's no way for an admin to retroactively pull chat logs after a participant has deleted them from their own view. This is a significant gap that catches a lot of organizations off guard, especially in regulated industries.
Get the Full Details
Using Google Vault for Historical Retrieval
Vault is the only tool that gives you a real historical archive of Meet activity at scale. You can create holds on Meet data for specific users or the entire organization, search across recordings and chats using keywords and date ranges, and export results in standard formats. The interface isn't fast—searches across large datasets can take ten to fifteen minutes—and the export process is manual, meaning you have to initiate each one yourself. There's no API-based bulk retrieval option built into Vault itself. I configured Vault holds for about two hundred users during a merger when we needed to preserve communication records. The initial setup took roughly two hours because you have to assign holds user by user through the Vault interface, and the hold confirmation emails sometimes don't reflect the actual scope of the hold until you run a query. Once the holds were active, we were able to export meeting-related data going back to the point where retention rules were in place. Before Vault was configured, we had no access to anything older than the standard audit log retention window.
Limitations and What Doesn't Work
Google Meet simply does not provide a meeting history page that lists past calls with timestamps, participant names, and duration all in one view. This is a persistent complaint in the Workspace community and it hasn't changed despite repeated feature requests. Third-party integrations through the Google Workspace Marketplace claim to offer this kind of functionality, but most of them only work with Google Calendar event metadata rather than actual Meet session data. They can tell you when a Meet link was created but not who participated or what happened during the call. Another limitation that matters a lot is the gap between scheduled meetings and ad-hoc meetings. If someone starts an unscheduled Meet through the Google Meet homepage without going through Calendar, that meeting may not appear in Calendar-based reports at all. The audit logs will catch it, but the reporting granularity drops significantly. I've seen situations where an internal investigation needed meeting records and the only evidence available was a fragmented audit entry with no participant list and no recording. Those gaps are real and they compound quickly if your organization relies heavily on unscheduled video calls.
Practical Steps for Regular Users Without Admin Access
If you're not an admin and you just need to find your own past Meet activity, check your Google Calendar first. Every scheduled meeting with a Meet link appears there with the full details. Check your Google Drive under Recent files for any recordings you may have started. Look through your Google Chat history if the meeting had an active chat component. Your Gmail inbox will have the original invitation and any follow-up messages related to the meeting. There's no single dashboard that aggregates all of this, and Google doesn't provide a "Meet History" page for individual users. The best practical approach is to enable cloud recording going forward and make sure your organization sets up Vault retention rules early, because once data ages out of the audit logs or falls outside Vault holds, it's essentially gone. I wish I'd done that setup before the audit came up, but the process of configuring everything retroactively took far longer than it would have upfront. If you need detailed historical meeting analytics—attendance trends, participation patterns, meeting duration statistics across teams—Google's native tools won't give you that level of analysis. You'd need to export the CSVs from individual meeting reports and build your own aggregation in a spreadsheet or BI tool, or look into dedicated meeting intelligence platforms that integrate with Workspace. Those tools exist but they're additional costs on top of your existing subscription, and they still depend on the quality of data Google exposes through its APIs, which is limited compared to what competitors like Zoom provide in their native dashboards.
