What Google Slides is
Google Slides creates and delivers slide presentations within Google Drive and Workspace. It combines browser editing, collaboration and mobile access. Personal access and additional organisation-plan features coexist.
The working unit is a shared presentation. Authorised people contribute content and review comments before delivery. Value depends on organising that review: permission to edit does not make every contribution equally validated.
For OSH, it supports joint session preparation, explanation of results and meetings between sites. Distinguish projected slides from detailed documentation retaining sources, conditions and agreements for later consultation.
Reference documentation: Google Slides product overview.
History: Tonic, Zenter and shared presentations
Google announced its acquisition of Tonic Systems in April 2007, bringing presentation creation and conversion technology. In June it acquired Zenter, a web-presentation company founded by Wayne Crosby and Robby Walker and backed by Y Combinator.
Google Docs presentations launched on 17 September 2007 with browser import, editing and collaboration. The original announcement described 25 languages. That is a launch fact, not a current language limit.
In June 2014 Google introduced the Android Slides app with PowerPoint editing and announced iOS as forthcoming. Mobile development complemented browser work. Current guidance should distinguish device and account capabilities instead of repeating older descriptions unchanged.
Cloud Connect, an earlier Microsoft Office synchronisation plug-in, stopped working on 30 April 2013. Its retirement illustrates why historical integration guidance should not be treated as current instructions.
Reference documentation: Google acquires Tonic Systems, April 2007 · Y Combinator: Zenter founders and acquisition · Google presentations launch, 17 September 2007 · Google Slides mobile launch, June 2014 · Cloud Connect discontinued on 30 April 2013.
Templates, themes and slide structure
A theme groups fonts, colours and layouts; the background sits behind content, while the layout arranges elements. Templates combine these resources with sample slides. Themes can be imported from compatible presentations.
For a series of prevention briefings, prepare slide types with clear purposes: observed situation, explanation, proposed measure and group question. Consistency supports comparison and updates without rebuilding the session.
Test real text and translations. A template suited to short titles may overflow with technical terms. Decide when to split a slide and what belongs in supporting documents rather than shrinking text until unreadable.
Reference documentation: Themes, layouts, backgrounds and templates.
Images, audio, video and playback permissions
Slides supports YouTube or Drive videos and MP3 or WAV audio stored in Drive. Playback options determine how a video starts. An access checker can suggest permission changes for audiovisual files in the presentation.
Test through the recipient’s account, not only the author’s. Visible images and playable video have different dependencies. Check sound, start, end and time for explaining the clip.
In OSH, choose material representing the situation being discussed. Label incorrect practice before it can be interpreted as a model. Prepare a description or alternative image preserving the essential message if playback fails.
Reference documentation: Images, video, audio and file permissions.
Linked charts and slides: what becomes visible
Linked charts, tables and slides display content from another file. Google warns that presentation recipients can see these objects without access to the original file. Source updates can override adjustments made at the destination.
For prevention indicators, inspect exactly what the object reveals before sharing. A restricted spreadsheet may feed a chart exposing figures to another audience. Review visible content as well as source permissions.
Decide whether the deck records a closed period or should update. Retain the meeting version when reconstructing decisions matters. Label period, population and unit to avoid interpreting changing data as a comparable trend without checking.
Reference documentation: Linked charts, tables and slides and their visibility.
Co-authoring and closing a delivery version
Collaboration brings contributions and comments into a common deck. Assign section owners and distinguish wording corrections, data changes and technical disagreements. An unresolved suggestion should not become a settled final message.
For cross-site preparation, record purpose, audience, period and reviewers. Keep this in the working record when it should not appear in the delivered presentation.
Agree who consolidates the file and how later changes are controlled. Review the full sequence after modifications: a corrected figure may leave an obsolete conclusion elsewhere. Retain references supporting important claims.
Delivery, notes and audience questions
Slides offers full-screen delivery and presenter view with notes. Audience tools receive and display questions and retain recent sessions for review. Test them using the meeting’s actual accounts and environment.
In an OSH briefing, explain suitable questions and how case-specific issues will be reviewed. Avoid requesting personal information in questions that may be displayed publicly. Rephrase sensitive questions before projection.
Use notes to support explanation, not conceal essential information. A distributed file needs enough context for independent consultation. Question counts indicate participation, not understanding or subsequent application.
Reference documentation: Present slides and speaker notes · Audience questions and Q&A history.
Sharing, publishing and skipping slides
File sharing and web publication are different actions. Publication can widen the audience and depends on account configuration. Skipping a slide does not delete it: people with file access can still see it.
Before distribution, inspect skipped slides, notes and material from other sources. Audience copies should contain suitable content. Open the result as a recipient would.
Assign responsibility for updating and removing presentations embedded in websites. Publication does not establish a fixed archive. Before reusing a campaign link, verify what it shows and whether the necessary context and review remain intact.
Reference documentation: Publishing a presentation to the web · Skipped slides remain in the shared presentation.
Recordings and camera presence inside slides
Slides recording is available to certain accounts and saves to Drive. It requires Chrome or Edge, editing access and storage; each recording is limited to 30 minutes. Recording information is absent from presentation revision history.
Speaker spotlight places camera video inside a slide shape. In Meet, the guidance describes tab sharing; sharing a window or whole screen disables spotlight. Availability depends on browser and account.
Before recording prevention content, check camera, background and result access. Review the entire video: correcting a slide afterwards does not necessarily update the earlier recording. Identify both versions and remove obsolete consultation copies.
Reference documentation: Slides recordings and requirements · Speaker spotlight in Slides and Meet.
Accessibility and live-caption limitations
Slides supports screen readers and keyboard navigation through notes and slides. Live captions show microphone-captured speech and are not retained as transcripts. The browser handles speech processing; administrators may restrict the feature.
For training, test technical terms, numbers and negations with the actual microphone. One word can change a sentence’s meaning. Prepare reviewed written material for points requiring precise consultation.
Design for different access methods: purposeful titles, described images and links understandable outside their context. Test without relying on colour or position. Review understanding of distributed material as well as its on-screen appearance.
Reference documentation: Live caption behaviour and limitations · Using Slides with a screen reader.
Offline work and continuity rehearsal
Offline work requires advance preparation in a compatible environment. This does not automatically make external videos, links and connected services available without a network.
Before a visit, test with the device disconnected. Traverse all slides, open necessary resources and identify information available only in other files. Retain an authorised alternative for essential content.
After reconnection, verify local changes at their destination. If multiple devices were involved, review the consolidated result before reuse. Reproduce the trainer’s actual workflow rather than merely checking whether the file opens.
Reference documentation: Offline preparation in Docs, Sheets and Slides.
PowerPoint exchange, exports and file capacity
Google distinguishes editing Office files from conversion to Slides, which creates a copy. The documented limit for presentations converted into Slides is 100 MB. Size limits do not guarantee exact preservation of another application’s elements.
After import or export, check text, fonts, charts, links and media. Compare the audience version with the original. Decide how animation-dependent explanations will work in static copies.
Retain editable sources and distributed files with consistent names. For OSH sessions, version and review date identify the material used. Avoid identically named copies with different content circulating without an update owner.
Reference documentation: Edit and convert Office files · Google Drive file limits.
Gemini: generation, editing and feature status
Gemini in Slides can generate images and slides, summarise and rewrite content, and reference Drive files. It requires an eligible plan. Advanced generation and editing documentation reviewed specifies desktop and English; interface language is not the same as support for each feature.
Google also documents full-deck generation with an initial outline and context sources. Some multi-slide editing capabilities are described in beta programmes. Actual availability depends on account, programme and rollout; check the option present before planning work.
For OSH, supply reviewed sources and retain conditions and exceptions in the outline. Review structure first, then every claim. Generated images can illustrate but should not be represented as inspection evidence or actual workplace photographs.
Assistant conversation is not equivalent to content saved in the deck. Retain sources and editorial decisions in the working record. Inspect generated objects: editability does not establish that their data or labels are correct.
Reference documentation: Collaborate with Gemini in Slides · Generate and edit slides with Gemini · Multi-slide editing beta scope · Generate a full presentation with Gemini.
APIs and Apps Script for repeatable presentations
The Slides API creates and modifies presentations, text, shapes and tables. Batch updates are validated together: an invalid request prevents the batch from applying. Apps Script provides a presentation service that saves changes at completion or explicit closing.
A proposed use is a monthly report generated from a template and reviewed data. Separating reading, calculation and layout helps locate errors. Define behaviour for missing values or source changes during generation.
Check content and appearance. Error-free execution may still leave a clipped title or a chart from the previous period. Acceptance should inspect figures, units, references, permissions and display on the intended device.
Reference documentation: Google Slides API overview · Atomic batches and revision control · Apps Script presentation lifecycle.
Practical applications in OSH
In occupational safety and health, it can support jointly prepared sessions and meetings across sites or departments. Different people can review examples, data and messages in a single presentation, with a named owner consolidating the content and confirming the version to be used. Collaboration should make responsibilities clear rather than leaving approval implicit.
Other proposed uses include presenting cross-site priorities and preparing induction sessions with a common core and local examples. Identify common slides and those requiring site-specific validation. Collaboration adds value when it reveals real differences, rather than forcing workplaces with different conditions to use identical instructions.
Worked example and result checks
For the incident-learning session, each site contributes an anonymised example with three fields: confirmed fact, agreed measure and available evidence of its outcome. The consolidating team checks that photographs belong to the case and that a hypothesis has not become a conclusion in a slide title. Comments help resolve disagreements before presentation.
Name the version intended for use and check permissions after review closes. Rehearse with the actual account and equipment, including video links. If live captions will be used, test the microphone and technical terms at the start; the speaker should verbally correct any recognised word that changes meaning. Supply a reviewed summary of agreements rather than relying on retrieving the presentation captions afterwards. Assign someone to record unanswered questions separately so they are not mistaken for confirmed findings in later summaries.
Limitations and conditions of use
Shared editing can introduce changes after review. Define a release version and control permissions, and verify videos and links before the session. Do not include unnecessary personal information or present an investigation hypothesis as a fact merely to simplify a slide.
When to choose it and how to complement it
Google Slides fits presentations prepared jointly by teams using managed permissions. Google Docs can preserve detailed agreements, while PowerPoint offers a comparison for editing and delivery in another environment.
Check connectivity, external participants’ accounts and the behaviour of downloaded copies. A useful trial opens links as the audience will, rather than only from an account with full access. Define who updates local slides after a common change and how the revised version reaches presenters who downloaded an earlier copy.
Frequently asked questions
Are presentation captions saved?
No, according to Google Slides help. If a record is needed, arrange an authorised method and review its output; displaying captions does not automatically create a retained transcript.
Does a visible link guarantee video playback?
No. Playback can depend on permissions, connectivity and file availability. Test with the audience’s role and prepare an alternative explanation of essential content.
Can a reviewed presentation still be edited?
Yes, when permissions allow it. Identify the version intended for use and control subsequent changes. Collaborative preparation needs a clear consolidation stage before delivery.
