--- title: "How to Convert PDFs into ServiceNow Knowledge Articles (5 Methods, Compared)" description: "ServiceNow cannot import a PDF as an article body. Here are the five ways to get PDF content into ServiceNow knowledge articles, what each one preserves, and which to use for ten files versus ten thousand." canonical: https://ocho.bot/blog/convert-pdfs-to-servicenow-knowledge-articles last_updated: 2026-09-12 --- # How to Convert PDFs into ServiceNow Knowledge Articles (5 Methods, Compared) > ServiceNow cannot import a PDF as an article body. Here are the five ways to get PDF content into ServiceNow knowledge articles, what each one preserves, and which to use for ten files versus ten thousand. Published: 2026-09-12 ServiceNow's Import Articles feature accepts Microsoft Word files only. There is no native option that turns a PDF into the body of a knowledge article. If you have PDFs and you want ServiceNow knowledge articles, you have five choices: attach the PDF, embed it inline, convert it to Word and import it, extract the text and load it through the API, or use an AI migration service that reads the PDFs and drafts the articles for you. This guide covers each method with the exact steps, what breaks, and which method fits which volume. ## The short answer - **Under twenty PDFs, and the PDF is already well written:** convert each to .docx, fix the headings, and use Import Articles. About ten minutes per file. - **PDFs that must stay PDFs (signed forms, vendor manuals):** attach the file to an article that summarizes it, or embed it inline with the Document Viewer. - **Hundreds of PDFs, and someone on your team can script:** extract the text, build HTML, and create articles through the Table API in small batches. - **Thousands of PDFs with duplicates, outdated versions, and no owner:** use an agentic migration. Ocho reads every file, drafts one article per topic with citations back to the source PDFs, and publishes only what your experts approve. Details in method 5. ## Why ServiceNow will not import your PDF The official import documentation lists one supported input: "Microsoft Word documents in the .doc and .docx file formats." ServiceNow's own support knowledge base has an article titled "Unable to import PDF, Excel and other file formats in the knowledge management application." On the community forums, the accepted answer to "How to import pdf documents to knowledge base" is the same: you can attach a PDF to an article, but you cannot import it as one. This is a design decision, not a bug you can work around with a setting. A knowledge article body is HTML stored in the `text` field of the `kb_knowledge` table. A PDF is a page-layout format. Something has to turn the layout into HTML, and ServiceNow has chosen to do that only for Word. ## Method 1: Attach the PDF to an article This is the fastest option and the one most teams use for vendor manuals and signed documents. 1. Create a knowledge article in the target knowledge base. Give it a short description that says what the PDF contains and who it is for. 2. Write a summary in the article body: what the document covers, when to use it, and the section people usually need. 3. Attach the PDF with the paperclip icon on the article form. 4. Publish the article through the knowledge base's workflow. What you get: the PDF is findable by the article's title and summary, and readers download or open it in the browser. What you lose: the article body does not contain the PDF's text. Search results, article snippets, and any AI feature that reads article bodies work only from your summary. The PDF's contents cannot be edited in ServiceNow, so every correction means replacing the attachment. ## Method 2: Embed the PDF inline If readers should see the PDF on the article page instead of opening an attachment, ServiceNow's Document Viewer can render it inside an iframe. Community members have documented the approach in several threads. 1. Attach the PDF to the article as in method 1, then copy the attachment's sys_id from the `sys_attachment` table. 2. In the article body's HTML source, add an iframe pointing at the viewer: ``. 3. Allow the iframe element and its `src`, `width`, and `height` attributes in the HTML sanitizer configuration, or the sanitizer strips the tag on save. Some teams instead disable the sanitizer on the `kb_knowledge.text` field, which lowers the security posture for every article. 4. Confirm the Document Viewer plugin is active on the instance. What you get: readers see the PDF without leaving the article. What you lose: the same searchability problem as method 1, plus a sanitizer change that your security team has to approve. The iframe height is fixed, so long documents scroll inside a box. ## Method 3: Convert the PDF to Word, then import it This is the only method that produces a real article body with native tooling. It works when the PDF was originally a text document and someone exported it to PDF. 1. Open the PDF in Microsoft Word (File, Open, choose the PDF) or export it from Acrobat as a Word document. Word rebuilds paragraphs, headings, lists, and tables. 2. Fix what the conversion missed. Apply Word's default Heading 1 through Heading 4 styles to the headings. ServiceNow imports only default heading styles, and it drops the numbers from numbered headings. Remove page headers, footers, and page numbers, because they arrive as body text. 3. Check every table. ServiceNow keeps table content but not table styling or borders. 4. Save as .docx with a lowercase file extension. The documentation requires the lowercase extension. 5. In ServiceNow, open All, Knowledge Articles, Import Articles (older releases: All, Knowledge, Import Articles). Choose the knowledge base and, optionally, a category. Leave Publish unchecked so the article lands in Draft for review, or check it to send the article into the knowledge base's publish workflow. Select the file and import. 6. Open the draft. Images from the Word file arrive as attachments and are embedded in the body, though the documentation warns that their alignment may differ from the original. Fix the layout, set the category and validity date, and move the article into review. What you get: an editable HTML article that search and AI features can read. What you lose: time. Layout-heavy PDFs (multi-column pages, forms, scanned images) convert badly. Scanned PDFs have no text layer and need OCR first. A 200-page manual becomes one 200-page article, which is not what a help desk wants. The import uses the standard article template only. ## Method 4: Extract the text and load it through the API When you have hundreds of PDFs, converting each by hand is not an option. The alternative is a script that extracts text, builds HTML, and creates articles through the REST Table API. ServiceNow's own import guide recommends the Table API for large batches. Extract text with a PDF library such as pdftotext, PyMuPDF, or pdfplumber. Turn the result into simple HTML: headings, paragraphs, lists, tables. Then create the article: New articles start in Draft under the knowledge base's workflow, and the article number is assigned automatically. If the article should also carry the original file, upload it with the Attachment API: Images inside the PDFs need separate handling. Extract them, upload each one as an attachment, and reference the attachment URL in the article HTML. The Easy Import spreadsheet route is an alternative to the API for text-only articles, but ServiceNow's guide describes it as suited to articles without embedded media, and community reports show HTML sometimes arriving as literal text when loaded through Excel. The Table API avoids both problems. What you get: every PDF becomes an editable article, at any volume, with the original attached. What you lose: quality control. The script cannot tell that three PDFs describe the same procedure, that one of them is from 2017, or that a 40-page document should become six articles. Every problem in the PDF library becomes a problem in the knowledge base. ServiceNow's guide also warns to import in small batches to avoid request timeouts, so plan for a run that takes hours, not minutes. ## Method 5: Agentic migration with Ocho Methods 3 and 4 convert files. They do not decide what the knowledge base should contain. At the volumes where method 4 becomes necessary, the deciding is most of the work, and it is the part nobody on the help desk has time for. Ocho is an AI knowledge orchestration platform built for this case. You point it at the PDFs where they live (a file share, SharePoint, a folder upload), and AI agents read every file and build a map of what the collection actually holds: which documents cover the same topic, which version is newest, and which have not been touched in years. Each file gets a verdict, keep, archive, or duplicate, with a logged reason. Duplicates collapse into one drafted ServiceNow article that cites the source PDFs, page by page. Your experts approve each article before it is published to ServiceNow, and after cutover new content is triaged automatically so the library does not accumulate the same problems again. The tradeoffs are the same as any managed service. It is done for you by a forward deployed engineer rather than by your admin, so it fits teams with thousands of documents and no one available to read them, and it does not fit a team with fifteen PDFs. The engagement is priced per deployment, and the entry point is a two-week, fixed-price triage of up to 10,000 pages whose report you keep whether or not you continue. The details are on the [SharePoint to ServiceNow migration page](/leave-sharepoint), which covers PDF libraries as one of its cases. ## Which method for which situation - **A signed policy or a vendor manual that must not change:** method 1 or 2. - **Fewer than twenty well-formatted PDFs:** method 3. - **Hundreds of PDFs, clean and non-duplicated, with a scripter available:** method 4. - **Hundreds or thousands of PDFs with duplication, unknown owners, or mixed quality:** method 5. - **Scanned PDFs:** OCR first, then method 3 or 4. Nothing else works on an image. ## What every method has in common A PDF is a document. A knowledge article is a unit of answer. The migration succeeds or fails on the mapping between the two, and no import tool does the mapping for you. Before you move anything, decide for each PDF: which knowledge base, which category, which ownership group, what the valid-to date should be, and whether the file should become one article or several. ServiceNow's article lifecycle (Draft, Review, Published, Retired) exists so that a human confirms each of those choices. Use it. Import into Draft, review, then publish. ## Questions ### Can Now Assist create a knowledge article from a PDF? Not as a documented feature. Now Assist for Knowledge Management generates draft articles from resolved incidents and cases. We found no ServiceNow documentation describing article generation from an uploaded file, and a community thread on the topic recommends building a custom skill. ### What is the attachment size limit? The property `com.glide.attachment.max_size` sets the maximum attachment size in megabytes. The documented default is 1024 MB, and your administrator may have lowered it. ### Does converting to Word preserve links? The documentation states that links are preserved for .docx files. Use .docx rather than .doc. ### Can the import handle several PDFs at once? Import Articles accepts multiple Word files in one operation and creates one article per file. There is no documented file count limit, but ServiceNow's community guidance is to import in small batches. ## Sources and how we checked Checked on 2026-09-12 against the ServiceNow Zurich documentation and the ServiceNow community. Where a claim comes from a community thread rather than the product documentation, the text says so. - ServiceNow docs: [Import a document as a knowledge article](https://www.servicenow.com/docs/bundle/zurich-servicenow-platform/page/product/knowledge-management/task/t_ImportADocument.html) and [Import Word documents](https://www.servicenow.com/docs/bundle/zurich-servicenow-platform/page/product/knowledge-management/task/import-word-platform.html) - ServiceNow docs: [Table API](https://www.servicenow.com/docs/r/api-reference/rest-apis/c_TableAPI.html) and [Attachment API](https://www.servicenow.com/docs/r/api-reference/rest-apis/c_AttachmentAPI.html) - ServiceNow docs: [Maximum attachment size](https://www.servicenow.com/docs/r/platform-security/instance-security-hardening-settings/sc-max-allowed-attachment-size.html) - ServiceNow community: [How to import pdf documents to knowledge base](https://www.servicenow.com/community/developer-forum/how-to-import-pdf-documents-to-knowledge-base/m-p/2776382), [Can we import PDF as Knowledge Article?](https://www.servicenow.com/community/servicenow-ai-platform-forum/can-we-import-pdf-as-knowledge-article/td-p/1155542), [PDFs in articles and Knowledge Base of documents](https://www.servicenow.com/community/knowledge-managers/pdfs-in-articles-and-knowledge-base-of-documents/m-p/2717934) - ServiceNow community: [Options for importing external articles into ServiceNow](https://www.servicenow.com/community/knowledge-management-articles/options-for-importing-external-articles-into-servicenow/ta-p/2673388) - ServiceNow docs: [Generate a knowledge article with Now Assist](https://www.servicenow.com/docs/bundle/zurich-it-service-management/page/product/knowledge-management/task/Now-Assist-generate-article-SOW-itsm.html) --- Ocho — AI knowledge orchestration · [Home](https://ocho.bot/) · [Docs](https://ocho.bot/docs) · [Blog](https://ocho.bot/blog) · [About](https://ocho.bot/about) · [Developers](https://ocho.bot/developers) · [Contact](https://ocho.bot/contact) · [llms.txt](https://ocho.bot/llms.txt)