Prepare for the holiday season with upgraded tROAS bidding, Checkout Links, and more from YouTube’s July Demand Gen Drop.
A look at how the Gemini app for macOS now lets you speak naturally to get clean transcriptions, edits, and summaries just using your voice.
Providing a safe online experience and protecting users from harm is a top priority at Google Play. We take this responsibility seriously and have been investing continuously to offer baseline protections on our platform while also empowering parents with the tools they need to make decisions for their families. Importantly, we also want to empower Play developers with the capabilities to deliver age-appropriate experiences based on their app's content.
To support this, today, we are taking another big step in our ongoing partnership with parents and developers by announcing the expansion of the Google Play Age Signals API to all Play developers globally. Building on current availability in Brazil, we will expand this experience first to users in Australia and Canada by mid-August, with a full global rollout to all users later this year.
The Play Age Signals API is a privacy-preserving tool that puts parents in the driver's seat allowing them to share their child's age range (e.g. 16-17) directly with apps. It also enables adults to easily share their age when prompted by the app developer. In turn, developers receive the signals they need to tailor their own in-app safety experiences and content for users in an age-appropriate way.
We want to give developers the ability to choose the right protections for the nature of their app. A weather app, for example, shouldn't need the same safety settings as entertainment or media apps. Rather than enforcing one-size-fits-all rules, we give developers the flexibility to choose how they integrate safety signals. With this reliable signal, you retain complete agency to tailor your app's content, features, and settings to match your audience.
.png)
Parents shouldn't have to manage complex safety settings across dozens of different apps to keep their children safe. The Play Age Signals API simplifies this by putting age-sharing controls in one place, directly inside the Google Family Link app. Parents have a choice to share their child’s age range, and if they choose to share, all Play apps that use Play Age Signals API can receive age signals. This lets children jump straight into age-appropriate content without parents having to manually configure settings inside these apps. Age ranges are never shared by default, and parents can update or turn off these settings at any time.
.png)
The Play Age Signals API builds upon a strong foundation of established safety features and strict policies we have long enforced on Google Play. Today, we already mandate that apps designed for families meet rigorous safety standards, and we continuously review and scan applications to ensure they are safe for children. For developers, we also offer built-in tools like Restrict Minor Access in the Play Console to help them manage who can discover their apps. For parents, Google Family Link remains a trusted, central dashboard where they can manage screen-time limits, PIN-based content filters, and app download approvals.
Expanding the Play Age Signals API globally adds a powerful new tool to our existing safety suite, helping parents and developers work together to make Google Play an even safer, more trustworthy place for families.
The Beta channel is being updated to OS version 16733.33.0 (Browser version 151.0.7922.56) for most ChromeOS devices.
If you find new issues, please let us know one of the following ways:
Visit our ChromeOS communities
General: Chromebook Help Community
Beta Specific: ChromeOS Beta Help Community
Interested in switching channels? Find out how.
Andy Wu
Google ChromeOS
A new LTS-144 version 144.0.7559.258(Platform Version: 16503.91.0), is being rolled out for most ChromeOS devices.
This version includes selected security fixes including:
515429352 High CVE-2026-11669 Integer overflow in Media on ChromeOS
495939973 Critical CVE-2026-8513 Use after free in Input
511742228 High CVE-2026-9979 Insufficient validation of untrusted input in Input
513774197 High CVE-2026-10982 Use after free in WebXR
517644287 High CVE-2026-11693 Inappropriate implementation in Plugins
517705966 High CVE-2026-11694 Use after free in ServiceWorker
513731890 High CVE-2026-11660 Insufficient validation of untrusted input in New Tab Page
518105731 High CVE-2026-11697 Insufficient validation of untrusted input in UI
517607902 High CVE-2026-11692 Use after free in Read Anything
515469283 High CVE-2026-11670 Use after free in PDF
517168239 High CVE-2026-11646 Use after free in ViewTransitions
517129549 High CVE-2026-11683 Use after free in WebCodecs
517486004 High CVE-2026-11689 Insufficient validation of untrusted input in Passwords
503929476 High CVE-2026-9952 Use after free in WebAudio
511736002 High CVE-2026-11651 Use after free in Network
513762354 High CVE-2026-10981 Insufficient validation of untrusted input in Codecs
517103584 High CVE-2026-11682 Insufficient validation of untrusted input in Views
516910450 High CVE-2026-11674 Use after free in Guest View
515465685 High CVE-2026-10988 Use after free in Views
513773313 High CVE-2026-11662 Type Confusion in Bindings
533446300 Critical CVE-2026-15901 Use after free in Network
513028160 High CVE-2026-9986 Insufficient validation of untrusted input in OptimizationGuide
497047552 High CVE-2026-7357 Use after free in GPU
513019760 High CVE-2026-9985 Insufficient validation of untrusted input in Media
518007484 Critical CVE-2026-15765 Use after free in Ozone
417052041 Medium CVE-2026-13860 Incorrect security UI in Autofill
527406824 High CVE-2026-15133 Use after free in InterestGroups
505815080 Critical CVE-2026-10888 Use after free in Cast Streaming
524045160 Critical CVE-2026-15129 Use after free in Views
Release notes for LTS-144 can be found here
Want to know more about Long-term Support? Click here
Andy Wu
Google Chrome OS
Earlier this month, we announced platform properties for Search Console, allowing you to track how your social and video posts on Instagram, TikTok, X, and YouTube perform on Google Search, Discover, and Google News. Today, platform properties are globally available to everyone.
The Extended Stable channel has been updated to 150.0.7871.212 for Windows and Mac which will roll out over the coming days/weeks.
Hi everyone! We've just released Chrome Stable 151 (151.0.7922.57) for iOS; it'll become available on App Store in the next few hours.
This release includes stability and performance improvements. You can see a full list of the changes in the Git log. If you find a new issue, please let us know by filing a bug.
Chrome Release Team
Google Chrome
As the use of AI becomes more prevalent, transparency is key. In the last week, we have launched updates in both the Campaign Manager 360 API and Display & Video 360 API that add new optional fields to resources in both APIs, which allow you to label a creative or creative asset as having been created or edited with AI. Labels will be applied to ads with such assets serving in regions with local AI labeling regulations. As of today, those regions are the European Union (EU), India, and New York state. Read more about AI content labeling at the Campaign Manager 360 Help Center and Display & Video 360 Help Center.
In both APIs, this configuration is set using the optional syntheticContentAttestationStatus field in relevant resources. Setting this field to IS_SYNTHETIC applies the label in the regions listed above, while setting it to NOT_SYNTHETIC confirms that the content does not require a label. You can also leave the field unset. A label will not be applied if the field is left unset. However, once the field is set for a resource, it can’t be unset and may only be updated to be either IS_SYNTHETIC or NOT_SYNTHETIC.
If you have any questions regarding the Campaign Manager API, contact Campaign Manager 360 API support. If you have any questions regarding Display & Video 360 API or Structured Data Files, or want to discuss this post, reach out to us on the #display-video-360-api or #structured-data-files channels on Discord.
In the Campaign Manager 360 API, this configuration is set in Creative resources. The syntheticContentAttestationStatus field can be set at resource creation using creatives.insert or updated for existing resources using creatives.patch and creatives.update.
For more information about how synthetic content labels work in Campaign Manager 360 API, see our guide page.
In the Display & Video 360 API, this configuration is set in Creative and AdAsset resources. The syntheticContentAttestationStatus field can be set at resource creation using advertisers.creatives.create, advertisers.adAssets.create, advertisers.adAssets.bulkCreate and advertisers.adAssets.upload. It can also be set or updated for existing resources using advertisers.creatives.patch and advertisers.adAssets.patch.
For more information about how synthetic content labels work in Display & Video 360 API, see our guide page.
Starting in Structured Data Files (SDF) v10.1, which is scheduled to launch in the coming weeks, you will be able to add labels when using YouTube videos as video assets in Ad files or as related videos in Line Item files. More details on this implementation will be provided in the upcoming launch announcement of SDF v10.1 and the associated reference documentation.
- Trevor Mulchay, Display & Video 360 API Team
You can now create and edit images, diagrams, and infographics directly alongside your text using Gemini in Google Docs. These images leverage the context of your document, so you can generate relevant visuals to accompany your writing without ever leaving Docs or relying on external tools. Plus, you can refine your existing visuals and graphics using simple natural language prompts.
With this new functionality, you can:
You can access these capabilities from the bottom bar or the Gemini side panel in Google Docs.
Note: This feature is currently supported on the web only.
