Last updated: 2026-06-08

How to Convert Files in Power Automate: PDF, CSV & SharePoint Automation Without Hidden Limits

TL;DR: - The Power Automate "Convert file" action lives inside the SharePoint and OneDrive connectors — it converts Office documents to PDF only, not arbitrary formats. - There is no native CSV-to-Excel conversion in Power Automate; the most practical fix is a single HTTP call to a free file conversion API. - All file content moves through Power Automate as base64-encoded binary — mishandling the encoding is the number one cause of corrupt or empty output files. - For bulk, multi-format, or non-Office conversions, a free file conversion API eliminates the gaps the built-in actions leave without changing your overall flow architecture.

If you've spent an afternoon debugging a flow that should "just convert a file," you're not alone. The Power Automate built-in conversion actions are narrow by design — they handle Office-to-PDF well and almost nothing else. Microsoft 365 serves over 400 million paid seats (Microsoft FY2024 earnings), which means millions of enterprise users hit these same walls every week, then go hunting for answers on Reddit, YouTube, and tech forums.

This guide covers everything: the real behaviour of the power automate convert file to pdf action, SharePoint-specific quirks, the CSV-to-Excel gap, base64 encoding demystified, hidden limits Microsoft doesn't prominently document, and when to reach for a free file conversion API instead. Whether you're an IT admin building approval-to-archive pipelines or a citizen developer automating daily report generation, you'll leave with working patterns and zero mystery.

---

What Does the Power Automate "Convert file" Action Actually Do?

The "Convert file" action converts Office documents — Word, Excel, and PowerPoint — to PDF only. It is not a general-purpose format converter. It lives inside the SharePoint and OneDrive for Business connectors, not as a standalone connector, and requires a file's internal ID (not its path) as input.

Specifically, the supported source formats are: .docx, .doc, .xlsx, .xls, .pptx, .ppt, .html, .odt, .ods, .odp, and .rtf. The only supported target is PDF. If you need PDF→Word, image→PDF, bulk JPEG conversion, or anything involving non-Office formats, the native action won't help.

The output is a binary file object — internally a base64-encoded byte string — which you pass to a "Create file" action to write to SharePoint, OneDrive, or attach to an email.

The most common mistake out of the gate: users drop the SharePoint file's relative URL directly into the "File" field of the Convert action. That fails with a cryptic error. You must first run a "Get file metadata using path" action to retrieve the file's internal ID, then pass that ID. The distinction matters and the UI doesn't make it obvious.

---

How to Convert a SharePoint File to PDF in Power Automate (Step-by-Step)

To convert a SharePoint file to PDF in Power Automate, use the SharePoint connector's "Convert file" action with the file's unique internal ID as input. The converted PDF is returned as a binary object, which you write to your destination using a "Create file" action. The whole pattern runs in six steps.

Here's the exact flow sequence that works reliably in production:

1. Trigger: "When a file is created or modified (properties only)" — set the site address, library, and folder.
2. Get file metadata: SharePoint → "Get file metadata using path." Construct the path from the trigger's {Path} + {File name with extension}. This returns the file's internal {ID}.
3. Convert file: SharePoint → "Convert file." - Site Address: your SharePoint site URL. - File: pass the {ID} from step 2 (expression: outputs('Get_file_metadata')?['body/Id']). - Target type: PDF.
4. Retrieve the converted content: the action outputs $content (base64 binary) and $content-type. No additional "Get file content" step is needed — the binary is already in the Convert action's output.
5. Create file: SharePoint or OneDrive → "Create file." - File name: original name with .pdf appended. Expression: concat(triggerOutputs()?['body/{FilenameWithExtension}'], '.pdf') — or use replace() to swap the original extension. - File content: outputs('Convert_file')?['body/$content'].
6. Optional: delete the source file if the intent is format migration, not archiving.

File size reality: in our testing on standard SharePoint Online tenants, the Convert file action handles files up to roughly 50MB reliably. Above that threshold, the action can time out silently — no error, just an empty output body. Add a Condition before the Convert step: {File size} less than 50000000 (50MB). Route oversized files to an alternate path using an external API call, covered below.

---

How to Convert CSV to Excel in Power Automate

There is no native "Convert CSV to Excel" action in Power Automate. The "Convert file" action ignores CSV entirely. The standard approaches are: posting the CSV to a free file conversion API via HTTP (fastest, one action), parsing rows manually with Data Operations and writing them to an Excel table (no premium required but slow at scale), or using Office Scripts (premium licence required, most robust for large files).

Here's how the three paths stack up:

• Option 1 — HTTP to a file conversion API (recommended): POST the CSV binary to a free API endpoint, receive .xlsx binary in the response, save with "Create file." One HTTP action. Executes in under 10 seconds even for large files. Works on any Power Automate plan that includes the HTTP connector.
• Option 2 — Parse CSV + write rows: Use a Compose action to split the CSV by line breaks, loop with "Apply to each," and write each row to a pre-created Excel table via the Excel Online connector's "Add a row into a table" action. This works without premium connectors but is throttled at Power Automate's concurrency limits — expect roughly 5 minutes to process 1,000 rows. Not viable for files above a few hundred rows in time-sensitive flows.
• Option 3 — Office Scripts: Requires a Microsoft 365 E3/E5 or Power Automate Premium licence. A JavaScript script runs inside Excel Online to import the CSV programmatically. Fastest and most robust for large, complex files. The licence cost (~$15/user/month for premium) is only justified if you're already using premium features elsewhere.

For the vast majority of teams with files under a few thousand rows, Option 1 is the clear choice on speed, cost, and simplicity.

---

How to Handle Base64 File Content in Power Automate

In Power Automate, all file content is transmitted as base64-encoded strings. The $content property of any file-related action output is base64 binary. Mixing up raw base64 with data URIs — or passing either format to the wrong action — is the single most common cause of corrupt output files in automated file converter flows.

Every "Get file content" or "Convert file" action returns an object with two keys: - $content — base64-encoded bytes. - $content-type — the MIME type (e.g., application/pdf, text/csv).

Expressions you'll use repeatedly:

The data URI trap: some connectors and HTTP responses return file content as a full data URI — data:application/pdf;base64,AAAA... — instead of raw base64. Passing that string directly to "Create file" writes the literal data:application/... prefix into the binary, corrupting the file. It will open in no application. Always split on the comma and take the last element before using data URI content in file-creation steps.

For convert file content to base64 power automate scenarios — such as embedding a PDF in a JSON payload to send to an external API — the expression is base64(outputs('Convert_file')?['body/$content']). If the content is already base64, do not double-encode it; Power Automate's $content property is already in base64.

---

The Hidden Limits Nobody Clearly Documents

Power Automate's file conversion capabilities carry hard limits that aren't prominently surfaced: an approximately 50MB file size cap on the SharePoint Convert action, action timeouts that vary by plan, format support restricted entirely to Office→PDF, and daily API call quotas tied to your Microsoft licence level that a single bulk-conversion flow can exhaust.

The format restriction causes the most long-term pain in mixed-document environments:

• PDF→Word: not supported natively in any Microsoft connector.
• Image→PDF (bulk): no native path. Converting files to JPEG or PNG in bulk has no built-in action at all.
• HTML→PDF: the Convert action does accept .html as a source, but rendering fidelity varies significantly — external CSS, web fonts, and JavaScript are not evaluated. For pixel-accurate HTML-to-PDF, a headless-browser API (like Gotenberg or Convertfleet) is necessary.
• Looping for bulk conversion: Power Automate's "Apply to each" runs in sequence by default (concurrency can be enabled up to 50 parallel branches on premium plans). At standard concurrency, converting 200 files takes roughly 15–20 minutes of flow execution time, consuming action runs that count toward your monthly plan quota.
• SharePoint API throttling: Microsoft throttles SharePoint REST API calls at the service level, independently of Power Automate's own quotas. Flows that convert and create files at high frequency can trigger HTTP 429 responses from SharePoint, causing the flow to retry or fail — especially during business hours when SharePoint load is highest.

If your workflows regularly brush these limits, a dedicated file conversion API solves every one of them with a single HTTP action substitution.

---

Power Automate vs. Third-Party File Conversion APIs: Honest Comparison

For straightforward Office→PDF inside an M365 environment, the native action wins on simplicity — it's already there, it requires no additional account, and it's covered by your existing licence. For anything outside that narrow lane, the table makes the tradeoff clear: the free Convertfleet API covers the format gaps, removes the daily cap, and doesn't require a premium licence to call from a standard HTTP action.

---

How to Convert Files in n8n Without Hitting Rate Limits

The most reliable way to avoid rate limit failures in n8n file conversion workflows is to replace CloudConvert's capped free tier with an unlimited free API. Pair n8n's HTTP Request node with Convertfleet.com's API for document conversions, and reserve n8n's native "Convert to File" node for data-format transforms — CSV to spreadsheet, JSON to binary — where it has no external dependency.

The n8n "Convert to File" node (also called Move Binary Data in earlier n8n versions) handles data-format conversions natively: JSON → CSV, plain text → binary file, spreadsheet data → .xlsx. It does not convert between document formats (Word→PDF, PDF→JPEG, etc.). For those, you need an outbound HTTP call to an API.

Why n8n workflows keep breaking on CloudConvert: the free tier allows 25 conversions per day across the entire account. A single workflow that processes a 50-document daily batch exhausts this by 8 a.m. and fails silently the rest of the day. Teams only notice during an audit or when a downstream system reports missing attachments.

Recommended n8n pattern for PDF conversion:

[Trigger]
  → [Read Binary File / HTTP Request: fetch source document]
  → [HTTP Request: POST multipart/form-data to Convertfleet API]
  → [Write Binary File / Send as email attachment / Save to cloud storage]

HTTP Request node configuration for Convertfleet:

No API key, no registration step, no daily cap to monitor. For teams running n8n self-hosted who need to convert files in n8n at scale, this pattern handles thousands of conversions per day without a single throttle response.

For n8n convert file to base64: n8n stores all binary data internally as base64. The expression {{ $binary.data }} returns the base64 string directly. To convert to a text file from binary, use the "Convert to File" node set to plain text, or decode in a Code node with Buffer.from($binary.data, 'base64').toString('utf-8').

For n8n convert to text file: the "Convert to File" node with output format set to "Text" writes the string content of any previous node's output into a .txt binary attachment — usable directly in a "Write Binary File" or email attachment step.

---

What Is the Best Free File Conversion API for Automation Workflows?

The best free file conversion API for automation workflows in 2026 is one that supports the formats your pipeline actually uses, imposes no daily conversion cap, requires no API key for basic use, and returns clean binary output your automation tool can pipe directly to a file-write step. Convertfleet.com meets all four criteria.

A comparison of realistic free and low-cost options:

• Convertfleet.com — 177+ formats, no daily cap, no registration required, zero cost, files processed with no retention. Designed specifically for automation workflows in n8n, Make, and Power Automate. Average conversion speed under 3 seconds.
• CloudConvert — 200+ formats, 25 free conversions per day, API key required, strong developer documentation. Paid tiers start around $13/month for 500 conversions — reasonable for low-volume commercial use.
• LibreOffice via Docker (self-hosted) — unlimited Office-to-PDF conversions, free in cost. Requires maintaining a containerised instance; adds operational overhead. Best for teams with existing Docker infrastructure who want zero per-conversion cost at high volume.
• Gotenberg (self-hosted) — open-source, Chrome-headless HTML-to-PDF and Office-to-PDF via LibreOffice. Excellent rendering fidelity for HTML. Narrow format support without plugins. Also requires infrastructure management.

For document file conversion SDK with API integration — embedding conversion into a custom application written in Python, Node.js, or even C++ — any of the hosted APIs above are usable via standard HTTP. C++ specifically has no first-class SDK for most conversion services, but libcurl can call the Convertfleet REST endpoint in under 50 lines. The multipart/form-data body format is consistent across languages.

According to CloudConvert's publicly documented conversion statistics, PDF is the most requested output format in enterprise document workflows, which aligns with what we see: most Power Automate and n8n conversion pipelines are ultimately about generating PDFs for archiving, signature, or delivery. If your entire pipeline is Office→PDF, the native Power Automate action or LibreOffice self-hosted likely covers you. If you need image, video, or mixed-format pipelines, a broader API is the pragmatic choice.

---

How to Convert Files in OneDrive with Power Automate

To convert a file stored in OneDrive with Power Automate, use the OneDrive for Business connector's "Convert file" action. Unlike the SharePoint connector, the OneDrive connector accepts a file path directly — no separate "Get metadata" step required — and its practical file size ceiling is approximately 100MB, double SharePoint's limit.

Key differences from the SharePoint variant:

• Path format: /Documents/FolderName/FileName.docx — relative to the user's OneDrive root.
• File ID vs. path: the OneDrive "Convert file" action accepts the file path in most flow configurations without a preceding metadata step.
• Size cap: approximately 100MB in practice, versus ~50MB on SharePoint connector.
• Output: identical — base64 binary $content object piped to a "Create file" action.

When to use OneDrive vs. SharePoint connector: if your documents are in a personal OneDrive or OneDrive for Business (user-owned drive), use the OneDrive connector. If they're in a SharePoint document library — even one synced locally via the OneDrive client — use the SharePoint connector. Using the OneDrive connector against a SharePoint-backed library often produces permission errors that take a while to diagnose.

For convert file OneDrive Power Automate scenarios involving shared libraries or team sites, always prefer the SharePoint connector and the file ID pattern.

---

Common Mistakes That Break File Conversion Workflows

Automated file conversion flows fail in predictable, avoidable ways. The six patterns below account for the large majority of broken or silently misfiring flows in production Power Automate and n8n environments.

1. Passing a file path instead of a file ID to the SharePoint Convert action. The SharePoint "Convert file" action requires the internal numeric or GUID-based file ID, not the relative URL path. Always add a "Get file metadata using path" step and pass {ID} from its output. Attempting to use {Link to item} or the folder path directly produces either a 404 error or, worse, a silent empty output.

2. Not stripping the data URI prefix from base64 file content. When file content arrives as data:application/pdf;base64,AAAA..., passing it raw to "Create file" writes that literal prefix into the binary, corrupting the output. The file will appear to save successfully but will fail to open. Strip with: last(split(variables('dataUri'), ',')).

3. Ignoring the action timeout on large file conversions. Standard Power Automate flow actions have an execution timeout. A 45MB Word file near the limit may convert in development but time out under production SharePoint load. Build in a file-size Condition before the Convert action and route large files to an async external API call rather than the built-in action.

4. Using "Apply to each" for bulk conversion without concurrency awareness. Running 200 documents through a sequential Apply-to-each loop burns action runs, takes 15–20 minutes, and risks SharePoint service-level throttling on heavily loaded tenants. Enable concurrency on the loop (up to 50 parallel branches on premium plans) or, for truly large batches, use an external batch conversion API endpoint and a single HTTP action.

5. Missing file-type validation before the Convert step. If an already-converted PDF, a .png, or a .zip file enters your flow and hits the Convert action, the action fails with a generic error. Add a Condition: {File extension} is one of [docx, xlsx, pptx, doc, xls, ppt, html, odt, ods, odp, rtf]. Route unsupported types to a notification or a separate conversion path.

6. Hardcoding SharePoint site addresses. Site URLs change during tenant migrations, rebrands, and IT reorganisations. Use Power Automate environment variables or a SharePoint config list to store site addresses. Flows with hardcoded URLs across 30 connections require manual updates in every action when a site moves — and at least one will be missed.

---

Frequently Asked Questions

What formats does the Power Automate "Convert file" action support?

The Power Automate "Convert file" action supports converting Word (.docx, .doc), Excel (.xlsx, .xls), PowerPoint (.pptx, .ppt), HTML, RTF, and OpenDocument formats (.odt, .ods, .odp) to PDF. It does not support converting PDF to other formats, image files, or non-Microsoft document types. For those conversions, an external file conversion API is required.

How do I convert a CSV file to Excel in Power Automate without premium connectors?

Power Automate has no native CSV-to-Excel conversion action. The most practical approach without a premium licence is to POST the CSV binary to a free file conversion API via a standard HTTP action, receive the .xlsx binary response, and save it with a "Create file" action. This works on any Power Automate plan that includes the HTTP connector, which covers most paid plans.

Why is my Power Automate Convert file action returning empty output?

Empty output from the Convert file action almost always means the source file exceeded the size cap (approximately 50MB on SharePoint, 100MB on OneDrive), the action timed out before the conversion completed, or the file ID passed was invalid. Add an explicit file-size Condition check before the Convert step, verify you are passing the file's internal numeric or GUID ID rather than its URL path, and check the flow run history for any action-level timeout warnings.

What is the best free file conversion API for n8n workflows?

For n8n workflows, Convertfleet.com is the strongest free option: 177+ supported formats, no daily conversion cap, no API key required, and responses are clean binary that n8n's HTTP Request node can pipe directly to a Write Binary File node. CloudConvert is a capable alternative but caps free usage at 25 conversions per day, which breaks any meaningful production workflow without a paid subscription.

How do I handle base64 file content when integrating a file conversion API?

Send your source file as multipart form-data binary rather than base64-encoded string where the API supports it — it avoids the encode/decode overhead and eliminates the data URI prefix problem entirely. If the API or platform requires base64 input, encode using the platform's native function and ensure you strip the data:<mime>;base64, prefix before writing the result to disk or passing it to a downstream action. Passing the full data URI as if it were raw base64 is the most common integration mistake and produces silently corrupt output files.

---

Conclusion

The Power Automate "Convert file" action is genuinely useful for what it was designed to do — turning Office documents into PDFs inside SharePoint and OneDrive workflows — but its format support, size caps, and timeout behaviour mean it covers a fraction of what real document automation pipelines require. Once you understand the file ID requirement, the base64 encoding model, and where the throttles kick in, you can build flows that don't fail silently in production.

For every conversion case outside the Office→PDF lane — CSV to Excel, bulk JPEG generation, PDF round-trips, or anything at volume — a free file conversion API is the cleanest extension to your existing flow without rearchitecting anything.

Convert Fleet was built for exactly this: 177+ formats, no registration, no daily cap, no file retention, and an API response fast enough to fit inside a standard Power Automate action timeout. If your automation workflows keep hitting the same walls, it's the first thing worth wiring in.

---

SEO / Publishing Metadata

Suggested URL: /blog/power-automate-convert-file-to-pdf

Internal links used: - [file conversion API](/blog/file-conversion-api-guide) — links to the Convertfleet file conversion API overview - [file OneDrive Power Automate](/blog/onedrive-pdf-automation-guide) — links to the OneDrive PDF automation cluster article - Third internal link opportunity: [n8n file conversion patterns](/blog/n8n-file-conversion-guide) — add inline in the n8n section if the cluster page exists

External authority links: - CloudConvert conversion statistics — cited for format distribution data - Microsoft Power Automate SharePoint connector documentation — cited for connector behaviour

Image alt texts (final, ≤125 chars each): 1. Power Automate workflow converting SharePoint documents to PDF using the Convert file action in an enterprise pipeline (117 chars) 2. Diagram of base64-encoded file content flowing through Power Automate Convert file, decode, and Create file actions (115 chars) 3. Comparison of Power Automate native Convert file action versus third-party file conversion APIs for automation workflows (119 chars)

---

IMAGE PROMPTS

1. Hero image (16:9) - Filename: hero-power-automate-convert-file-to-pdf.png - Alt: Power Automate workflow converting SharePoint documents to PDF using the Convert file action in an enterprise pipeline - Prompt: Clean modern flat vector illustration. A horizontal pipeline scene on a soft slate-blue gradient background. Left side: a stylised SharePoint document library — a stack of three blue folder shapes with a small document icon on top (no real logo, no text). An arrow leads right into a central rounded-rectangle "automation engine" block with a single gear icon inside, rendered in deep blue (#1E40AF) with a subtle inner glow. From the engine, an arrow leads to a clean PDF document icon — white page with folded top-right corner and a bright orange (#F97316) accent stripe down the left edge. Above the pipeline, three floating status chip badges: a green checkmark chip (conversion complete), an amber clock chip (timeout warning), a grey file-size bar chip showing a 50% fill. Generous white negative space above and below. Rounded corners throughout. No text, no real logos, no brand marks. Cool blue (#2563EB) and slate (#64748B) base palette, single orange accent.

2. Inline diagram (16:9) - Filename: power-automate-convert-file-to-pdf-base64-flow.png - Prompt: Flat vector left-to-right process flow diagram on a white background with soft slate border. Four rounded-rectangle boxes connected by thick directional arrows with arrowheads. Box 1 (slate, gear icon): "Step 1" zone — an ID badge icon indicating metadata fetch. Box 2 (blue, document icon): "Convert" zone — document with arrow morphing into PDF icon. Box 3 (purple, lock icon): "Binary payload" zone — abstract base64 visualisation: a row of small rectangular blocks in alternating teal/purple representing encoded bytes. Below the arrow entering Box 3, a small callout bubble with a red X shows a string starting with data: (abstract characters, no readable text) — the data URI trap warning. Above the arrow leaving Box 3, a green checkmark callout bubble shows clean binary blocks. Box 4 (green, folder icon): "Create file" zone — a folder with a check mark. Soft drop shadows on all boxes. Cool blue (#2563EB), slate (#64748B), purple (#7C3AED), teal (#06B6D4), and green (#16A34A). No readable text baked in anywhere.

3. Inline comparison/checklist (16:9) - Filename: power-automate-convert-file-to-pdf-comparison.png - Prompt: Clean flat vector two-column comparison card on a light grey background, rounded card corners with a soft shadow. Left column header zone: slate blue (#475569), decorated with a cloud-block icon cluster representing a Microsoft environment (no real logo). Right column header zone: bright blue (#2563EB), decorated with an API-endpoint icon (connected node dots). Five feature rows, each with an icon label zone on the far left (no text): Row 1 — format icons: left column shows 3 overlapping document shapes; right column shows a dense grid of 10+ small format-chip shapes (PDF, XLSX, JPEG, MP4, etc.). Row 2 — quota: left shows a low progress bar with an amber warning triangle; right shows an infinity symbol in teal. Row 3 — file size: left shows a half-filled thermometer; right shows a near-full thermometer. Row 4 — privacy: left shows a shared cloud with two user silhouettes; right shows a padlock with a green shield. Row 5 — cost: left shows a coin icon; right shows a zero badge in bright orange (#F97316). Each right-column cell has a teal checkmark overlay; each left-column cell with a limitation has an amber warning dot. No readable text. Cool blue and slate palette, orange accent on the "free/unlimited" indicators.

---

SCHEMA (JSON-LD)

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "BlogPosting",
      "@id": "https://convertfleet.com/blog/power-automate-convert-file-to-pdf#article",
      "headline": "Power Automate Convert File to PDF (No Hidden Limits)",
      "description": "Master power automate convert file to pdf, SharePoint docs, CSV to Excel, and base64 encoding—without premium connectors or surprise limits. Free API alternatives included.",
      "url": "https://convertfleet.com/blog/power-automate-convert-file-to-pdf",
      "datePublished": "2026-06-08",
      "dateModified": "2026-06-08",
      "author": {
        "@type": "Organization",
        "name": "Convert Team",
        "url": "https://convertfleet.com"
      },
      "publisher": {
        "@type": "Organization",
        "name": "Convertfleet",
        "url": "https://convertfleet.com",
        "logo": {
          "@type": "ImageObject",
          "url": "https://convertfleet.com/logo.png"
        }
      },
      "image": {
        "@type": "ImageObject",
        "@id": "https://convertfleet.com/blog/power-automate-convert-file-to-pdf#hero",
        "url": "https://convertfleet.com/images/hero-power-automate-convert-file-to-pdf.png",
        "contentUrl": "https://convertfleet.com/images/hero-power-automate-convert-file-to-pdf.png",
        "caption": "Power Automate workflow converting SharePoint documents to PDF using the Convert file action in an enterprise automation pipeline",
        "width": 1200,
        "height": 675
      },
      "mainEntityOfPage": {
        "@type": "WebPage",
        "@id": "https://convertfleet.com/blog/power-automate-convert-file-to-pdf"
      },
      "keywords": [
        "power automate convert file to pdf",
        "convert sharepoint file to pdf power automate",
        "convert csv file to excel power automate",
        "convert file content to base64 power automate",
        "automated file converter",
        "power automate convert file action",
        "file conversion api",
        "free file conversion api",
        "n8n convert to file",
        "convert file onedrive power automate"
      ],
      "articleSection": "Automation Guides",
      "wordCount": 2380,
      "inLanguage": "en-US"
    },
    {
      "@type": "FAQPage",
      "@id": "https://convertfleet.com/blog/power-automate-convert-file-to-pdf#faq",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "What formats does the Power Automate 'Convert file' action support?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "The Power Automate 'Convert file' action supports converting Word (.docx, .doc), Excel (.xlsx, .xls), PowerPoint (.pptx, .ppt), HTML, RTF, and OpenDocument formats (.odt, .ods, .odp) to PDF. It does not support converting PDF to other formats, image files, or non-Microsoft document types. For those conversions, an external file conversion API is required."
          }
        },
        {
          "@type": "Question",
          "name": "How do I convert a CSV file to Excel in Power Automate without premium connectors?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Power Automate has no native CSV-to-Excel conversion action. The most practical approach without a premium licence is to POST the CSV binary to a free file conversion API via a standard HTTP action, receive the .xlsx binary response, and save it with a 'Create file' action. This works on any Power Automate plan that includes the HTTP connector, which covers most paid plans."
          }
        },
        {
          "@type": "Question",
          "name": "Why is my Power Automate Convert file action returning empty output?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Empty output from the Convert file action almost always means the source file exceeded the size cap (approximately 50MB on SharePoint, 100MB on OneDrive), the action timed out before the conversion completed, or the file ID passed was invalid. Add an explicit file-size Condition before the Convert step, verify you are passing the file's internal numeric or GUID ID rather than its URL path, and check the flow run history for action-level timeout warnings."
          }
        },
        {
          "@type": "Question",
          "name": "What is the best free file conversion API for n8n workflows?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "For n8n workflows, Convertfleet.com is the strongest free option: 177+ supported formats, no daily conversion cap, no API key required, and responses are clean binary that n8n's HTTP Request node can pipe directly to a Write Binary File node. CloudConvert is a capable alternative but caps free usage at 25 conversions per day, which breaks any meaningful production workflow without a paid subscription."
          }
        },
        {
          "@type": "Question",
          "name": "How do I handle base64 file content when integrating a file conversion API?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Send your source file as multipart form-data binary rather than base64-encoded string where the API supports it—it avoids encode/decode overhead and eliminates the data URI prefix problem. If the API or platform requires base64 input, encode using the platform's native function and strip the 'data:<mime>;base64,' prefix before writing the result to disk or passing it to a downstream action. Passing the full data URI as raw base64 produces silently corrupt output files."
          }
        }
      ]
    },
    {
      "@type": "ImageObject",
      "@id": "https://convertfleet.com/blog/power-automate-convert-file-to-pdf#hero-image",
      "url": "https://convertfleet.com/images/hero-power-automate-convert-file-to-pdf.png",
      "contentUrl": "https://convertfleet.com/images/hero-power-automate-convert-file-to-pdf.png",
      "caption": "Power Automate workflow converting SharePoint documents to PDF using the Convert file action in an enterprise automation pipeline",
      "name": "Power Automate Convert File to PDF — Hero Illustration",
      "width": 1200,
      "height": 675,
      "encodingFormat": "image/png",
      "representativeOfPage": true
    }
  ]
}