Version | Shell Build

Templates and components

Templates and component fixes may be released separately from new versions of Google Web Designer:

Release notes

A new version of Google Web Designer is available! 1 issue has been fixed in this release. Read below for additional details.

Updating Google Web Designer

Google Web Designer automatically updates upon launch if you have an internet connection. You can also download the latest version.

Compatibility changes:

Custom components that follow the Custom Elements v0 specification are no longer be supported. Learn how to upgrade your components.

Fixes & improvements in version

  • Fixed mask animation in Safari browsers.

Fixes & improvements in Shell Build

  • Fixed issue with importing files by dragging and dropping them into Google Web Designer.

Changes in version

  • Added Ads Creative Studio as a dynamic data schema option.

Known issues

  • Safari only: <canvas> elements with drawings prevent the animation of clip path masks.
  • Chrome and Opera: Clip path masks render incorrectly when the host element contains a 3D-transformed child element.
  • References to custom Google Web Designer elements (gwd-image, gwd-video, gwd-audio, gwd-iframe, gwd-page, and gwd-pagedeck) may not work as expected. Learn how you can update your references.
  • Timeline animation events, such as pause or loop, do not work when you directly open the source .html file in your browser. This is expected behavior, as timeline animation CSS is generated when previewing or publishing the document. Solution: use the Preview button, or publish the document locally and view the published file in your browser.
  • Image files without a file extension with a period in the file name don't import into the Library. Workaround: add the file extension (such as .png) to the file name.
  • A black screen on launch may be caused by outdated video drivers. Try updating your video drivers. If that doesn't help, disable GPU rendering by quitting Google Web Designer and following the instructions for your operating system before relaunching:
    • Windows: Add a DWORD32 value named disable-gpu-rendering to HKEY_CURRENT_USER\Software\Google\Web Designer\Settings in the registry. Set this value to 1.
    • Mac: Add a Boolean row to ~/Library/Preferences/ with the name disable-gpu-rendering and a value of YES, or run defaults write disable-gpu-rendering -bool true in Terminal.
    • Linux: Add a line to ~/.local/share/google-web-designer/preferences/settings.conf with the name disable-gpu-rendering and a value of true. (If the [Settings] section doesn't exist, you'll need to create it first.)
  • For a video to autoplay when an ad is re-expanded on Mac Safari, the first video source should be .mp4.
  • Gradient background fill on an image only renders when scaling is set to stretch.
  • A maximum of 4 panels can be grouped/tabbed together.
  • White screen on launch if behind a web proxy. Please follow these instructions to change your proxy settings.
  • Mac Chrome and Opera: Play button doesn't work in Google Web Designer preview when Autoplay preview is on. Workaround: remove localhost from the URL to use file:///
  • Linux only: file drag and drop from the file system to Google Web Designer is not working. Workaround: use File > Import assets or Add asset from the Library.
  • Downloading iCalendar .ics files is not supported on Safari desktop browser.
  • It is not possible to have more than one Map component or Street View component, or a Map and a Street View component in the same creative.
  • Linux only: if the browser (Chrome or Firefox) is launched by Google Web Designer for preview, Google Web Designer cannot be closed unless the browser is closed first.
  • Linux only: Google Web Designer sometimes loses focus and is unable to take keyboard input when switching between apps. Workaround: resize the Google Web Designer window to bring focus back to the app.
  • Linux only: if the renderer crashes and a white screen appears, set the disable-gpu-rendering to true in Google Web Designer settings. Add a row to ~/.local/share/google-web-designer/preferences/settings.conf with the name disable-gpu-rendering and a value of true. (If the [Settings] section doesn't exist, you'll need to create it first.)
  • Video ads: On Mac, making edits quickly, such as duplicating clips, can cause the stage to stop showing videos and for playback to not work, or for the UI to freeze. Workaround: relaunch Google Web Designer.
  • Video ads: A small gap appears between videos during slide or wipe transitions at certain stage zoom levels. The gap will not be visible in the exported video. Workaround: adjust the stage zoom.
  • Video ads: If copying a clip to another document is undone, the clip’s asset is not automatically removed from the Library. Workaround: manually delete the asset from the Library.
  • Video ads: If a video or audio asset file is manually overwritten with a different file in a project’s assets directory, the old asset continues to appear on the stage and in the exported video if any resolution other than full is used. Workaround: delete the asset and re-add it using the Library.
  • Video ads: Asset import errors may appear when opening a Google Web Designer project which was created on a different operating system (e.g., opening a file on Windows that was originally created on a Mac). Workaround: use File > Save As zip... to export and share a project.
  • Video ads: When zoomed out in the timeline, very short clips (e.g., 1 frame long at higher document frame rates) can stop showing and appear as empty space, even when selected. The clips are not deleted. Workaround: zoom in to see the clips.
  • Video ads: Certain malformed assets (e.g., videos created using some video ripper software) do not play or export properly in Google Web Designer.
  • Video ads: Certain colored text can have a slight drop shadow in the exported video (compression artifact).
  • Backdrop elements animated along a curved motion path, or nested within another element with a curved motion path animation, may not show filter effects during animation playback on the stage. The filters will behave as expected in the exported video and while scrubbing the playhead.

Was this helpful?

How can we improve it?
Clear search
Close search
Google apps
Main menu