What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
There is no documented one-line CSS fix for bold text that changes spacing in a Power Apps PDF. First identify the conversion route, then compare the rendered control with the PDF, verify the font and bold face, and test a minimal sample. Microsoft documents that “font weights and styles such as bold and italic may not appear in the generated PDF for some fonts,” so the defect can be in PDF rendering rather than in your HTML.
Identify which Power Apps conversion route you are using
“HTML to PDF in Power Apps” can describe different pipelines. The troubleshooting path depends on which one is actually running.
Native canvas-app PDF function
The experimental canvas-app PDF function exports a screen or supported control into a PDF object. It is not documented as a general-purpose arbitrary HTML conversion API. You enable it under the app’s experimental features, select the screen or control, and can provide options such as paper size, DPI, margins, orientation and container expansion. Generation occurs on the device, so device capacity is relevant.
Microsoft’s documented limitation is explicit: Non-Latin script types and font weights and styles such as bold and italic may not appear in the generated PDF for some fonts.
That warning makes font substitution or missing bold faces a primary suspect when spacing changes.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
A flow or connector that receives HTML
A Power Automate flow may store HTML, create a file, and then call a conversion connector. This is a different workflow from exporting a canvas screen. The Content Conversion connector documentation warns about converting HTML to plain text; that warning means formatting is discarded in that operation and should not be presented as a diagnosis of the native PDF function.
A third-party HTML-to-PDF connector
Microsoft’s connector catalog lists a Pascalcase HTML-to-PDF connector. Its listing establishes that it exists, not that it fixes bold spacing. Check its current licensing, regional availability, limits and service terms before selecting it.
Use a controlled comparison before changing CSS
- Render the source in the app. View the HTML Text control or rich-text output at the exact size used for export. Record the font family, weight and any letter-spacing rule.
- Open the generated PDF beside the app view. If spacing is already wrong in the control, investigate the markup and control properties. If the control looks correct and only the PDF differs, concentrate on font support and the PDF renderer. This comparison separates a source-markup problem from a conversion-stage problem.
- Reduce the sample. Create one line containing regular, bold and italic text, plus a second line containing punctuation and numbers. Export only that control. A minimal reproduction is easier to compare across devices and routes.
- Change one variable at a time. Test the font family, then the way bold is represented, then layout properties. Do not change font, size, margins and HTML structure in one edit or you will not know which change mattered.
Check the font and the way bold is represented
Confirm the effective font family
The font named in your HTML may not be the font actually available to the Power Apps renderer or the device generating the PDF. Inspect the control’s Font property and the HTML’s family declaration. Test a font with a distinct, known bold face and compare it with your production font. The Microsoft limitation applies to “some fonts”; it does not identify a universal safe list.
Test semantic bold and CSS weight separately
Use a minimal pair such as:
<p>Regular text <strong>bold text</strong></p>
<p>Regular text <span style="font-weight:700">bold text</span></p>If one form survives export and the other does not, keep the form that works in your controlled sample. This is a diagnostic, not a Microsoft-certified fix. Avoid assuming that font-weight:700 will synthesize a real bold face; a renderer may substitute metrics that alter apparent spacing.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Look for inherited letter spacing
Inspect parent styles and the HTML Text control’s padding and size properties. A positive letter-spacing value can make bold text appear especially loose, while a negative value can cause collisions when a different bold face is substituted. Remove the declaration temporarily, export again, and restore it only if the PDF remains correct.
Account for HTML Text and Rich text editor behavior
HTML Text control
The HTML Text control renders HTML tags and exposes Font, Size and padding properties. Microsoft says it assumes relatively positioned HTML and notes that default browser styling for some elements may be removed. Therefore, a browser preview is not a perfect prediction of the control’s layout or of the PDF generated from it. Keep positioning and spacing explicit in the small test sample.
Rich text editor
If users enter content in the Rich text editor, inspect the HTML it emits before conversion. Microsoft says the editor removes script, style, object and unsupported HTML elements and attributes. A style assembled upstream may therefore never reach the PDF stage. Compare the editor’s output with the HTML that your flow or control actually receives; do not troubleshoot a CSS rule that has already been removed.
Verify native PDF scope and options
When using the native function, confirm that you pass the intended screen or supported control. Check options that can affect layout even though they are not established cures for bold spacing:
Free tools Windows power users keep installed
One-click scans. No signup required.
- Paper size and orientation: a change can reflow lines and make spacing look different at page boundaries.
- DPI: use a consistent value while comparing samples; changing it can alter rasterized appearance.
- Margins: verify that apparent spacing is not the result of a narrower text box.
- Container expansion: enable the documented expansion behavior when clipping or unexpected height is part of the symptom.
Export on the same device class when reproducing the issue. Microsoft documents that PDF generation runs on the device, so capacity and device context belong in your test record.
A repeatable diagnostic procedure
- Write down the route: native
PDF(...), a flow and connector, or another service. - Save the smallest HTML/control sample that shows the defect.
- Record the effective font family, size, weight, control type and device.
- Compare app rendering and PDF output side by side.
- Remove custom letter spacing and nonessential CSS.
- Test semantic
<strong>or<b>against an explicit CSS weight. - Test a second font with a supplied bold face.
- If rich text is involved, inspect the sanitized HTML emitted by the editor.
- For the native function, repeat with stable paper, DPI, margin and orientation settings.
- Keep the smallest change that corrects the output, then retest the complete document for wrapping, page breaks and non-Latin text.
Common symptoms, causes and fixes to test
| Symptom | Likely location | Test or corrective action |
|---|---|---|
| Bold looks correct in the app but is loose in the PDF | PDF font handling | Test another available font and a minimal bold sample; record the device and route. |
| Bold is missing entirely | Unsupported font weight or sanitized markup | Check the effective font, test <strong> and inspect Rich text editor output. |
| Spacing is wrong in both app and PDF | Source HTML or control styling | Remove inherited letter-spacing, verify padding and simplify the markup. |
| Only rich-text content loses formatting | Editor sanitization | Inspect emitted HTML; do not rely on removed style or unsupported attributes. |
| Text clips or wraps differently | PDF scope or layout options | Confirm the exported control, then check paper size, margins, DPI and container expansion. |
| Results differ by machine | Device-side generation or available fonts | Capture device details and reproduce with the same font and settings. |
When to choose a different conversion workflow
Use the native function when your requirement is exporting the current canvas screen or supported control and its experimental status is acceptable. Consider a connector-based route when your process already operates on an HTML payload or needs flow-managed files. Compare input scope, support status, font and CSS fidelity on your exact sample, regional and licensing availability, size and page limits, and storage or flow requirements. The available Microsoft documentation establishes the native function’s screen/control scope and experimental status; it does not establish that any alternative has better bold-font fidelity.
Do not treat a third-party listing as proof of a fix. Validate a real document containing your fonts, bold weights, page breaks and any non-Latin scripts before migrating production work.
Performance, reliability and evidence to retain
Keep the reproduction small while diagnosing, then test a full document because a local correction can change wrapping and pagination. Record the route, app version and experimental setting, device, font family, HTML, control properties, PDF options and before/after files. A reproducible package lets you distinguish a renderer limitation from a regression and gives a connector vendor or Microsoft support a concrete case.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Microsoft’s cited PDF page is prerelease documentation last updated March 22, 2024. Experimental status and limitations can change, so verify the current product documentation before standardizing a workflow.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If your actual requirement is a clean screenshot or PDF of a web page rather than a canvas control, ScreenshotNeo provides a single HTTP request. It accepts consent banners like a visitor, removes more than 60 known consent platforms, newsletter popups and chat widgets before capture, and lets you turn those steps off. Bot checks, blank pages, timeouts, failed loads and cache hits are not billed, and each response identifies the page verdict and billing status. Its MCP server exposes take_screenshot, get_page_info and capture_pdf to Claude, Cursor and other MCP clients.
See the ScreenshotNeo API documentation for all options. cURL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);The Free plan includes 1,000 screenshots each month without a card; paid plans start at $5 for 3,000. Create a free ScreenshotNeo account to try it.
Frequently Asked Questions
Does increasing DPI fix bold spacing?
Not necessarily. DPI is a documented PDF option, but the Microsoft documentation does not establish it as a remedy for font-weight or spacing defects.
Best Value
Can I force every font to render bold correctly?
No universal guarantee is documented. Test a font with an available bold face and verify the generated PDF on the device and route you will deploy.
Is the Content Conversion connector the same as Power Apps PDF?
No. The native function exports screen or supported control content; a connector workflow receives and processes data separately.
What should I send when escalating the issue?
Provide the minimal HTML, effective font, control type, conversion route, PDF options, device context and side-by-side source and PDF output.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
