Enhancing User Experience: Customizing SharePoint Document Preview

Troubleshooting SharePoint Document Preview: Common Issues and Fixes

SharePoint’s document preview helps users view files quickly without downloading them. When previews fail or behave unexpectedly it slows collaboration. This guide covers the most common SharePoint document preview problems, root causes, and practical fixes you can apply as a site owner or admin.

1. Preview shows “No preview available” or blank pane

Common causes

• File type not supported by Office Online Server (OOS) or Office Web Apps.
• Corrupted file or invalid file extension.
• Browser blocking mixed content or third‑party scripts.

Quick fixes

1. Confirm file type: Ensure the file is a supported Office format (Word, Excel, PowerPoint), PDF, or a format supported by your preview service.
2. Open directly in Office: Download and open the file locally to confirm it isn’t corrupted.
3. Check browser console: Look for blocked resources (mixed content, blocked scripts) and enable loading of secure content or allow the domain.
4. Test in another browser: Rule out browser-specific issues or extensions interfering with the preview.

2. Previews fail for PDFs

Common causes

• PDF handler not enabled (SharePoint Online uses built‑in viewer; on‑premises needs proper configuration).
• Custom MIME type or incorrect file headers.
• Large PDFs or complex content (forms, embedded fonts) causing timeouts.

Fixes

1. Validate MIME type: Ensure server returns Content-Type: application/pdf.
2. Enable PDF viewer: For SharePoint on‑premises, confirm Web Application supports the PDF viewer or configure a third‑party PDF viewer.
3. Optimize large PDFs: Reduce file size or split into smaller files; test again.
4. Fallback: If preview still fails, offer a direct download link or open in Adobe Reader.

3. Thumbnails not generating or incorrect

Common causes

• Thumbnail generation service disabled or delayed.
• Unsupported file types or files stored in nonstandard locations (e.g., external storage).
• Permissions blocking the previewer service from accessing files.

Fixes

1. Reindex the library: Force a reindex from Library Settings → Advanced → Reindex Document Library.
2. Check timer jobs / background services (on‑premises): Verify the thumbnail generation timer job (or equivalent) is running.
3. Verify permissions: Ensure system account or preview service account has read access.
4. Clear cache: Browser cache or SharePoint cache may serve stale thumbnails—clear and retest.

4. Office document previews show old or cached versions

Common causes

• Browser or SharePoint caching serving stale content.
• Versioning and check-out causing preview to show a prior published version.

Fixes

1. Hard refresh / cache clear: Ask users to refresh with Ctrl+F5 or clear browser cache.
2. Ensure latest version is published: Confirm the file’s latest checked‑in and published version is visible.
3. Disable aggressive caching: Adjust CDN / proxy cache settings or SharePoint caching configuration to respect changes.

5. Authentication or permission errors in preview pane

Common causes

• Preview service uses different authentication flow and cannot access files.
• Cross‑site or cross‑domain auth issues (cookies/third‑party cookies blocked).
• Anonymous access conflicts.

Fixes

1. Test with same user account: Confirm user can open the file directly—if not, address permission issues.
2. Configure auth for preview service: On‑premises, ensure OOS/WAC can authenticate to SharePoint; on cloud, ensure tenant settings allow previews.
3. Adjust cookie settings: Enable third‑party cookies or configure SSO so preview frames can authenticate.
4. Check alternate access mappings / URLs: Ensure preview service uses a URL that’s trusted and accessible.

6. Performance issues: preview is slow or times out

Common causes

• Large files, heavy content, or insufficient server resources.
• Network latency between SharePoint and preview service.
• Throttling or resource limits on Office Online Server / SharePoint.

Fixes

1. Optimize files: Reduce images, simplify slides, or split large documents.
2. Scale preview service: Increase OOS/WAC capacity or use SharePoint Online where Microsoft manages scaling.
3. Improve network path: Place preview service closer to SharePoint servers or use faster links.
4. Check logs: Review ULS (on‑premises) or diagnostic logs for timeouts and tune timeouts accordingly.

7. Embedded content (videos, macros) not rendering

Common causes

• Web viewer strips active content for security.
• Unsupported embedded objects or active content (VBA macros) won’t run in preview.

Fixes

1. Educate users: Explain that embedded active content won’t run in preview—download to run macros or videos.
2. Provide thumbnails or screenshots: For video-heavy docs, include an image or link to the hosted video.
3. Use supported formats: Convert embedded content to a supported, static format where possible.

8. Broken previews after migration or restore

Common causes

• Missing farm-level services or preview configuration after migration.
• Broken links, invalid URLs, or missing OOS/WAC bindings.

Fixes

1. Verify service configuration: Reconfigure OOS/WAC bindings and SSO as required.
2. Run health checks: Use SharePoint health analyzer and test page requests to the preview service.
3. Repair links: Update alternate access mappings, host headers, and ensure DNS resolves correctly.

Diagnostics checklist (quick)

1. Try another browser and incognito mode.
2. Open the file locally to confirm it opens normally.
3. Check file type and MIME headers.
4. Verify permissions and service account access.
5. Reindex library and clear caches.
6. Review server logs (ULS / OOS logs) for specific errors.
7. Test with a small sample file to isolate size/content issues.

When to escalate to Microsoft or your admin

• Repeated server-side errors in ULS or OOS logs you cannot resolve.
• Authentication flows involving complex SSO or federated identity.
• Preview failures across the entire tenant after an update—contact Microsoft 365 support.

Summary Most preview issues stem from unsupported file types, permissions/authentication, caching, or resource limits. Use the checklist above to quickly identify the root cause, apply the targeted fixes, and escalate when server-side or tenant-level configuration requires administrative access.