Embed Any Document Plus WordPress is a commercial plugin from developer awsmin that lets a WordPress site display Word, Excel, PowerPoint and PDF files inside posts and pages without visitors needing to download the file or install any extra software. It pulls documents from four cloud services — Google Drive, Microsoft OneDrive, Dropbox and Box.com — and renders them through a viewer, either hosted by the cloud provider or generated in the browser. It suits site owners who publish reports, contracts, presentations or spreadsheets as part of their content and want them readable on the page rather than locked behind a download link.
What the plugin actually does with a document
The core action is straightforward. A shortcode or a Gutenberg block is placed in the content, pointed at a file, and the plugin outputs an embedded viewer in that spot. The visitor scrolls, zooms and pages through the document inline. Nothing is converted to HTML and nothing is re-uploaded to a third-party conversion service in the way Scribd or SlideShare handle it, which matters if the file is confidential or the site’s design needs to stay consistent around the embed.
Four cloud sources are supported: Google Drive, Microsoft OneDrive, Dropbox and Box.com. Each has its own file picker inside the editor, so a document does not have to be downloaded and re-uploaded to the WordPress media library first. The plugin also handles files already sitting in the media library, which is useful for smaller sites that keep everything on their own hosting.
Format coverage is wide for office documents. Word files (docx, docm, dotm, dotx), Excel spreadsheets (xlsx, xlsb, xls, xlsm), PowerPoint decks (pptx, ppsx, ppt, pps, pptm, potm, ppam, potx, ppsm) and PDF are all listed as supported. That range matters because many simpler embed plugins handle PDF only, and a business that publishes quarterly spreadsheets alongside a written report would otherwise need two tools.
There are two rendering paths. A cloud-hosted viewer uses the provider’s own preview engine — Google Docs Viewer for Drive files, the Microsoft viewer for OneDrive, and native viewers for Dropbox and Box. A browser-based viewer renders locally instead. The distinction is practical: hosted viewers depend on the provider’s servers being reachable and on the file’s sharing permissions being set correctly, while the browser-based route keeps rendering on the visitor’s machine. The plugin exposes both so a site can switch if one route misbehaves.
Several smaller controls round out the experience. Embed heights can be set responsively so a document scales with the viewport rather than forcing horizontal scrolling on phones. The download link text is editable, and the file size label can be hidden — useful when a client-facing page should not advertise that a PDF is 40 MB. A caching option stores the viewer output, and there is a per-file “do not cache” switch for documents that change often. Gutenberg is supported with a dedicated Document block, and the changelog shows Visual Composer and Divi support added for page-builder users.
Where this fits, and where it does not
The clearest fit is an organisation that already stores documents in the cloud and wants them surfaced on a website. A law firm publishing client guides, a school posting syllabi and reading lists, a manufacturer hosting spec sheets, a membership site gating reports behind a login — all of these publish the same file in many places and would rather link to one canonical cloud copy than maintain duplicates in WordPress.
It also suits agencies building client sites where the client will update documents later. Because the source file lives in Drive or Dropbox, the client edits the original and the website reflects the change without anyone logging into WordPress. That workflow is the real selling point, more than the embed itself.
Freelancers with a single PDF to show once are the wrong audience. A plain link, or the browser’s built-in PDF handling, costs nothing and does the same job. The plugin earns its $39 when there are multiple documents, multiple formats, or an ongoing publishing rhythm.
There is a second poor fit worth naming. Sites that must keep every byte on their own server — some government, healthcare and defence-adjacent projects — will not want documents routed through Google or Microsoft viewer infrastructure at all. The browser-based viewer mitigates this, but the plugin’s headline convenience comes from cloud pickers, and that is the opposite of what an air-gapped or strict data-residency policy requires.
Strengths and limitations
Strengths
- Four cloud providers in one plugin, each with an in-editor file picker, so documents do not need re-uploading to WordPress.
- Broad office format support — Word, Excel, PowerPoint and PDF — rather than PDF alone.
- Two rendering modes (provider-hosted and browser-based) give a fallback when one viewer fails or is blocked.
- Responsive embed heights and a Gutenberg block mean documents behave sensibly on mobile and fit modern editing workflows.
- Fine-grained display controls: download link text, file size visibility, caching on or off per file.
- Long, active maintenance history with security fixes, including sanitisation work on embed attributes and a correction for WordPress 6.8+ text domain loading.
- Source files (JavaScript, HTML, CSS, PHP) ship with the purchase, so an agency can extend or restyle the output.
Limitations
- Cloud-hosted viewers depend on sharing permissions being correct. A Drive file left private will render as an error for visitors, and the plugin cannot fix that — it is a configuration problem the site owner has to diagnose.
- External viewer services are third parties. If Google or Microsoft changes an endpoint or deprecates a viewer, embeds break until the vendor ships an update. The changelog shows this has happened before, with a critical Box.com API URL change and a Google Drive fix.
- There is no self-hosted rendering engine for Office formats. The browser-based viewer is a fallback, not a full local Office renderer, so a strict no-third-party policy is not fully satisfied.
- Privacy and consent obligations sit with the site owner. Embeds contact Google, Microsoft, Dropbox or Box servers, which has GDPR and cookie-consent implications the plugin does not resolve on its own.
- Compatibility is declared up to WordPress 7.0.x, but the vendor does not state a minimum PHP version or list tested theme and page-builder combinations beyond Visual Composer and Divi.
- At $39 for a single-site licence tier typical of CodeCanyon, cost scales if many client sites need it — worth checking the licence terms before standardising on it across an agency portfolio.
How it compares with the alternatives
The realistic alternatives fall into three groups. The first is a general-purpose embed or oEmbed plugin, which usually handles PDFs and maybe Google Docs but rarely covers Excel, PowerPoint, OneDrive and Box in the same package. Those are lighter and often free, and for a site that only ever shows PDFs they are sufficient.
The second group is document-hosting platforms such as Scribd and SlideShare. These give a hosted viewer and a social layer, but the document lives on someone else’s branded page, analytics are limited, and the visual style is not the site’s own. Embed Any Document Plus keeps the document inside the site’s design and lets the original file stay in the owner’s own cloud storage.
The third group is custom development — a developer wiring up each provider’s API by hand. That produces exactly the behaviour a project needs, but it costs far more than $39 and creates a maintenance burden every time a provider changes something. The plugin’s value is that it absorbs that maintenance, and the changelog suggests the vendor does keep pace.
On capability, the plugin sits above free embed alternatives and below fully bespoke integrations. It competes on breadth of sources and formats rather than on depth of any single one.
Frequently Asked Questions
Does Embed Any Document Plus require visitors to install anything?
No. Documents render inside the page using the browser, so visitors need no plugins, extensions or downloads to read them. The plugin relies on either a cloud provider’s viewer or a browser-based renderer. Visitors simply see the document embedded in the post or page, which is the main reason sites use it instead of a plain download link.
Which file types can be embedded?
Word, Excel, PowerPoint and PDF files are supported. That covers docx, docm, dotm and dotx for Word; xlsx, xlsb, xls and xlsm for Excel; a long list of PowerPoint variants including pptx, ppt and ppsx; and standard PDF. Formats outside these groups, such as images or plain text files, are not part of the stated support list.
Can documents be embedded from Google Drive, Dropbox and OneDrive?
Yes, all four major cloud services are supported: Google Drive, Microsoft OneDrive, Dropbox and Box.com. Each has a file picker inside the WordPress editor, so files can be selected from the cloud without downloading and re-uploading them. Files already in the WordPress media library can also be embedded, which suits smaller sites that host everything themselves.
Is the plugin compatible with the Gutenberg block editor?
Yes. The vendor lists the plugin as Gutenberg-optimised and provides a dedicated Document block, with the block API version updated in a recent release. Support for Visual Composer and Divi was also added for page-builder users. The changelog shows Gutenberg compatibility fixes going back several years, so the block editor is a first-class target rather than an afterthought.
Verdict
Embed Any Document Plus WordPress is a sensible purchase for organisations that publish documents regularly and keep the originals in cloud storage. The combination of four providers, wide office format support and a Gutenberg block covers the common cases, and a 4.48 rating across 63 reviews with more than 2,800 sales suggests the plugin does what buyers expect. The maintenance record is the strongest argument in its favour — security fixes and provider compatibility patches appear consistently, which is what separates a usable embed plugin from an abandoned one.
Buyers should go in with clear eyes about the trade-offs. Embeds lean on third-party viewer infrastructure, so sharing permissions, consent requirements and provider API changes are the site owner’s problem to manage, not the plugin’s. Sites with strict data-residency rules should look elsewhere, and anyone embedding a single PDF should not pay for this at all. For everyone in between — agencies, membership sites, schools, businesses with a document library — it is a reasonable $39 that removes a recurring maintenance chore.
