In Google Takeout, select YouTube and YouTube Music, keep History, and choose JSON rather than HTML. ScreenSignals reads the Google Takeout ZIP on the parent’s device and accepts supported YouTube Watch History records from the latest 30 days.
Google Takeout is Google’s export tool. It lets an authorized account holder create a downloadable archive of information associated with a Google account. Downloading an archive does not delete the information from Google.
What Google Takeout does—and does not do
Takeout packages selected Google data into an archive that the account holder can download. For ScreenSignals, the useful part is YouTube History—not uploaded videos or a complete copy of every Google product.
- It does not give ScreenSignals access to a Google password.
- It does not delete the account’s YouTube history.
- It does not guarantee a complete record if history was paused, deleted, automatically deleted, or recorded under another account.
- Google currently says Takeout does not support selecting a custom time period for the export. ScreenSignals applies its own latest-30-days analysis window after the parent chooses the file.
Official sourceGoogle documents the export process, download delivery, supported formats, and current time-period limitation in How to download your Google data.
Step-by-step: create the right YouTube history export
These steps are for an adult parent or legal guardian who is authorized to use the account’s viewing information. A child should not operate ScreenSignals or perform the upload.
- Open Google Takeout in a desktop browser. Go to takeout.google.com and confirm the correct authorized Google account is selected.
- Choose “Deselect all.” A smaller export is faster to prepare and easier to inspect.
- Select “YouTube and YouTube Music.” Do not select unrelated Google products for a ScreenSignals report.
- Open “All YouTube data included.” Deselect everything, then select History. Other YouTube records are unnecessary for the core watch-history report.
- Change the history format to JSON. HTML is useful for a person reading a file, but JSON is the structured format ScreenSignals supports for the report pipeline.
- Choose a one-time export. Select “Export once” unless you independently want Google’s recurring-export option.
- Keep a normal archive format. A ZIP delivered by email is the simplest option for most parents. ScreenSignals accepts the Google Takeout ZIP directly, so there is no need to extract it first.
- Create the export and wait for Google’s email. Preparation time varies with account data and Google’s systems. Use the download link in Google’s completion email.
- Return to ScreenSignals as the parent. Choose or drag the downloaded Takeout ZIP into the guided import.
Download all parts that Google identifies as belonging to the export. The ScreenSignals flow will tell you when the selected archive does not contain a supported Watch History file.
Where the YouTube watch-history file lives
Folder names can vary by language and export version, but the archive commonly contains a structure similar to:
Takeout → YouTube and YouTube Music → history → watch-history.json
You do not need to locate or extract that file before using ScreenSignals. The browser checks the ZIP for supported Watch History. If you are inspecting the archive manually, look for the JSON history file rather than an HTML history page.
Common export problems
| What happened | Likely reason | What to do |
|---|---|---|
| No Watch History found | History was not selected, or this archive is one part of a split export. | Create a smaller History-only export or check the other archive parts. |
| HTML is present but JSON is missing | The history format was left as HTML. | Create a new export and change History to JSON. |
| The archive is extremely large | Uploaded videos, music files, or unrelated products were included. | Export only YouTube History for a smaller archive. |
| Recent videos are missing | The wrong account was selected, history was paused or deleted, or viewing happened signed out. | Confirm the actual viewing account and its history settings. |
What YouTube Watch History contains
A valid record can identify a viewing event with information such as a title, YouTube link, channel, and timestamp. That supports useful counts and comparisons, but it has important limits.
- A history event does not reliably state how many minutes were watched.
- Repeated rows can represent legitimate repeat viewing rather than duplicate data.
- Private, deleted, unavailable, or malformed videos may no longer provide enough public context for analysis.
- A timestamp can show when the event was recorded; it does not prove who was holding the device.
- Video metadata and captions can change or become unavailable after the viewing event.
These are reasons to present the result as signals for parent review, not as a perfect transcript of a child’s experience.
A parent’s privacy checklist
- Use a trusted personal device rather than a public or shared computer.
- Confirm you are authorized to use the account and viewing information.
- Export only the YouTube data needed for the report.
- Store the downloaded archive somewhere protected until you are finished with it.
- Delete local copies you no longer need using your device’s normal secure-deletion practices.
- Review the receiving service’s data practices before selecting the file.
With ScreenSignals, the original Google Takeout ZIP is read on the parent’s device and is not uploaded or stored as a file. Supported viewing entries and the analysis needed to maintain the private report are sent to and stored by the service. Read the complete ScreenSignals Privacy Notice before starting.
Use the export to understand the month
A JSON file is difficult to interpret by hand. ScreenSignals turns the latest 30 days of supported parent-provided history into a content mix, repeated formats, channels, evidence-backed signals, and conversation ideas. The parent can inspect the public videos behind important findings and decide what the family context means.