Does WorshipTools Work With Google Slides? What “Works” Hides

Yes. Presenter by WorshipTools works with Google Slides through a native Google Slides import: an authorized user opens the Google Presentation Picker from Presenter, selects a deck, and can sync later Google edits back into Presenter. The imported deck remains a Slides Library asset; it does not become native Song or Scripture items, and browser-only playback is merely projection rather than Presenter integration.

The label erases four operating conditions: who owns the deck, what travels, what stays editable, and which screen receives it. They determine whether Sunday starts with a cue list or a search through browser tabs.

What does “works with Google Slides” actually mean?

WorshipTools documents a direct import. In Presenter, the operator chooses Slides, Add Slides, and Import Google Slides; the Google Presentation Picker asks for account access and returns the selected deck to the Slides Library. WorshipTools says subsequent Google changes can be synced back into Presenter.

That is one of four workflows commonly hidden by the word “works”:

| Workflow | What Presenter receives | Where edits happen | Operational consequence | |---|---|---|---| | Native Google Slides import | A linked Slides Library asset | Google Slides, followed by a sync | Keeps the cloud deck as the source | | PowerPoint handoff | A downloaded `.pptx` file | Google Slides before export; PowerPoint afterward | WorshipTools converts the imported deck to static images | | Browser playback | A live browser presentation outside Presenter | Google Slides | Presenter cues, Remote and output rules do not control the tab | | Rebuilt service | Separate Song, Scripture, Slides and Media items | Presenter | Requires more preparation and exposes worship-specific controls |

Google’s Drive export-format reference identifies `.pptx` as the Microsoft PowerPoint export for presentations. WorshipTools’ PowerPoint/Keynote documentation says those imports become static images; preserving PowerPoint animations, transitions and video requires the Windows-only Launch with PowerPoint option. PowerPoint or Keynote must be installed for that WorshipTools import process.

WorshipTools’ product page names four cloud-synced presentation-asset categories—song lyrics, videos, images and cue lists—while its service builder documents six item types: Blank, Song, Scripture, Slides, Media and Web page. A Google deck enters one part of that system.

How does WorshipTools Presenter differ from ProPresenter for a Google deck?

WorshipTools offers the shorter Google-to-service route because its documentation provides a Google picker and later synchronization. Renewed Vision’s current ProPresenter documentation instead describes a `.pptx` bridge: download the Google deck as PowerPoint, then import that file.

ProPresenter version 21 changed that bridge. Renewed Vision says its native importer turns `.pptx` files into editable presentations while preserving applicable text, slide objects, media and simple animations. It excludes older `.ppt` files, charts, SmartArt, comments, advanced gradients and some animations or transitions.

WorshipTools makes a different trade in its PowerPoint route. Slides become images, while text and objects stop being independently editable. Its Google route avoids that export and preserves source updates through sync, but WorshipTools does not claim that Google elements become editable Presenter objects.

The documented comparison is therefore exact: WorshipTools has the direct Google link; ProPresenter 21 has the richer editable `.pptx` conversion. Neither route turns a sermon deck into structured lyrics or Scripture simply because the file opened successfully.

Which Presenter features disappear in a static slide workflow?

A static deck keeps pixels and sequence. Worship behavior requires the corresponding Presenter data.

• A cue list can contain the imported deck as one service item, but its internal slides do not become separate Song, Scripture or Media items. Fine-grained service changes require editing the deck or rebuilding selected content.
• Built-in Bibles and Quick Scripture remain outside the deck. WorshipTools documents Quick Scripture as a reference-based audience display; a verse baked into a slide cannot use that lookup.
• Lyric structure and timing do not arise from slide images. WorshipTools’ Loop Connect feature creates timed lyric slides from a setlist, whereas a static lyric deck advances according to its own slide order or the operator.
• WorshipTools Remote can control a Presenter session from iOS or Android when both devices have internet access and use the same account; Pro or Pro Plus is required. A Google Slides tab running by itself is outside that session.
• Multi-output layouts depend on Presenter screen rules. WorshipTools provides two built-in screen definitions, Main Audience Output and Stage Display, then permits additional screens on Pro or Pro Plus with no software-set limit beyond connected hardware. Template overrides on added screens apply only to Song and Scripture content, so a static sermon slide will not automatically become a lower third for the livestream.

WorshipTools’ system requirements add a hardware condition that the “unlimited” claim can obscure: at least two independent video outputs for extended desktop, or three when Stage Display is used. The computer’s physical output capacity remains the ceiling.

What must be checked before rehearsal?

Test the final machine, account and display path. A volunteer’s laptop proves little about the sanctuary computer.

1. Lock the handoff. Record the Google file owner, importing account, deck name and final-sync time. Choose either native import or `.pptx` handoff as the primary path; two half-maintained versions create an untraceable result.
2. Compare rendering. Open the title slide, the densest text slide, every nonstandard font and the final slide on the actual audience display. A screenshot from Google beside a photo of the projected result exposes substitution, cropping and aspect-ratio changes.
3. Fire every media cue. Google’s Editors Help supports two Drive audio formats in Slides, `.mp3` and `.wav`. WorshipTools’ Media Library lists seven local media types: JPEG, PNG, GIF, MP4 with H.264, MP3, M4A and WAV. Embedded video, audio and permissions still need an end-to-end play test.
4. Verify access from the operator account. Google says its access checker can suggest permission updates for embedded audio and video. The picker login, deck, audio and video must all open without borrowing the creator’s credentials.
5. Trace each output. Disable mirroring, identify Main Audience Output and Stage Display by physical screen, and confirm any livestream Window or NDI destination. Check the first and last cue on every active output, because a correct control monitor says nothing about the projector route.
6. Measure the network under service-like load. WorshipTools specifies a “reliable internet connection” but publishes no minimum Mbps. The FCC’s 100 Mbps download and 20 Mbps upload figure is a fixed-broadband benchmark, not a Presenter requirement. Record the venue test, then prove the synced service opens in WorshipTools Offline Mode; online-only YouTube and imports remain unavailable there.

Rehearsal needs the same discipline. Rundown Studio’s live-event guide recommends a one-to-one technical rehearsal—at least two hours for a two-hour show. Applied to a 60-minute service, that means a 60-minute run, with separate correction time. Maegan Stephens, Ph.D., Senior Director of Communication Services at Duarte, gives the useful test: “A rehearsal should feel as close to the real thing as possible.” Use the final computer, remote, account and screens.

What is the least risky way to use an existing Google Slides service?

Keep the finished deck and remove live improvisation from the handoff:

1. Duplicate the Google deck, date the service copy and give one editor authority over it.
2. Import that copy through Presenter’s Import Google Slides command rather than presenting from a loose browser tab.
3. Place the imported deck in the service cue list. Rebuild only the songs, Scripture or lower-thirds that genuinely need Presenter behavior.
4. Sync once edits close, then inspect the first, last, densest and media-bearing slides on every routed output.
5. Export a local `.pptx` and PDF from Google. If `.pptx` is the fallback inside WorshipTools, import and test it before rehearsal because the required desktop presentation application must already be installed.
6. Complete the full technical run, mark the tested version, and deny further edits unless the presentation lead and operator repeat the affected cue.

This route preserves the Google Slides work and gives Presenter control of service order without treating a visual deck as lyric timing, Bible references or adaptive screen layouts.

What backup should the operator have when one part fails?

Every fallback should already be open or locally stored. A plan beginning with a password reset has already failed.

| Failure | Prepared backup | Operator action | |---|---|---| | Cloud sync or venue internet | Last verified service opened on the presentation computer, plus local media and dated exports | Enter Offline Mode and avoid YouTube or new cloud imports | | Google Slides browser tab | The natively imported Presenter service | Continue from the matching cue in Presenter | | Remote phone or tablet | Keyboard or mouse at the booth and a named booth operator | Transfer control verbally at the next agreed cue | | Stage or second display | A documented single-screen route, spare cable and tested adapter | Keep Main Audience Output; suspend the failed secondary feed |

WorshipTools says Offline Mode loads the most recent version previously accessed on that computer. That sentence contains two conditions: “most recent” is limited by the last successful access, and another computer’s update is irrelevant until synchronization completes.

How should the team document one repeatable workflow?

Use a one-page run sheet, revised after each service. It should name the Google source owner and importing account; the primary import method; the edit cutoff and recorded sync time; the Presenter service name; the font and media exceptions; the physical output map; and the local fallback filenames. Attach a short cue log with the actual rehearsal result, failure found, correction made and person who verified it.

The source-of-truth rule belongs at the top: Google Slides remains authoritative until the edit cutoff, and the tested Presenter service becomes authoritative afterward. If a late change crosses that boundary, its owner must sync it, rerun the affected cue and record the new time and operator.

Frequently asked questions

Which audio files are compatible with Google Slides?

Google Docs Editors Help says Google Slides can add `.mp3` and `.wav` audio files stored in Google Drive. The file’s sharing permissions must also allow the presenting account to open it. WorshipTools separately accepts MP3, M4A and WAV in its Media Library, so the two compatibility lists are not identical.

What can Google Slides not do?

Google Slides cannot provide WorshipTools’ structured Song and Scripture items, Loop Connect lyric timing, Presenter Remote control or per-output Song and Scripture template overrides. It can display a prepared deck and collaborate in the cloud. Those worship-production functions require Presenter data and a service configured inside Presenter.

Can Google Slides be used with ProPresenter?

Yes. Export the Google Slides presentation as a Microsoft PowerPoint `.pptx` file, then import it into ProPresenter. Renewed Vision says ProPresenter 21 can preserve editable text, objects, media and simple animations, although `.ppt`, charts, SmartArt, comments and some effects or transitions are excluded from its native importer.

Where are the tools in Google Slides?

Google places the menus and toolbar across the top of an open Slides presentation. Its Tool finder also sits at the top and searches commands or recommends actions. Google’s shortcut reference says to open Tool finder with Alt+/ on Windows or ChromeOS and Option+/ on macOS.

Does WorshipTools Presenter support PowerPoint?

Yes. WorshipTools Presenter imports PowerPoint presentations, but its documentation says the normal import converts slides to static images and requires PowerPoint or Keynote on the computer. On Windows, Launch with PowerPoint can preserve animations, transitions and video by opening the deck in PowerPoint during the service.

Where can I find WorshipTools Presenter documentation?

WorshipTools publishes Presenter documentation in the Docs & Tutorials section of its website. The Presenter categories cover system requirements, services, screens, songs, slides, Scripture, media, cloud storage, Remote and Stage Display. The Google Slides page sits under Presenter → Slides → Google Slides.

Can a shared Google Slides deck be imported as editable Presenter slides?

A shared deck can be selected through WorshipTools’ Google Presentation Picker when the importing Google account has access. WorshipTools describes the result as a Slides Library import that can resync Google changes; it does not document conversion into editable Presenter text and objects. Keep editing the source in Google Slides.