PC 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 & 11Outdated 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 matchIf bold text has incorrect spacing in a Power Apps PDF, do not start by changing random CSS declarations. First identify the conversion route, compare the content before and after conversion, and test the actual font and bold face being rendered. Microsoft documents that bold and italic styles may not appear in generated PDFs for some fonts, but its documentation does not promise one universal fix for every spacing defect.
This guide gives you a controlled way to isolate the problem in a canvas app, an HTML Text control, a Rich text editor pipeline, or a flow-based conversion.
1. Identify which Power Apps PDF route you are using
“Converting HTML to PDF in Power Apps” can describe different workflows. The remedy depends on which one your app actually calls.
Native canvas-app PDF function
The experimental PDF function exports a screen or supported control content into a PDF object. It is not documented as a general-purpose arbitrary-HTML conversion API. The function must be enabled under the app’s experimental features, and generation occurs on the device running the app. Options include paper size, DPI, margins, orientation, and expansion of some containers.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
HTML stored or sent through a flow
An app may store HTML, pass it to Power Automate, and use a connector or service to create a file. That is a separate rendering path. A connector warning about converting HTML to plain text means formatting is discarded in that operation; it should not be treated as a statement about the native Power Apps PDF renderer.
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. Verify its current licensing, regional availability, limits, and service terms before adopting it.
2. Compare the source with the generated PDF
Make a two-stage comparison before editing the document.
- Open the screen or HTML Text control in the app and inspect the bold text at normal zoom.
- Generate the PDF using the same data and capture the resulting file.
- Compare letter spacing, word spacing, font weight, line breaks, and clipping.
- Repeat with a minimal sample containing one normal sentence and one bold sentence.
If the spacing is already wrong in the app, the problem is upstream of PDF generation. Inspect the HTML, control properties, editor output, and font selection. If the app looks correct but the PDF changes the spacing or loses the weight, concentrate on the PDF renderer and the font available to it. This comparison is a diagnostic inference, not a guarantee that every discrepancy has the same cause.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →3. Verify the font and the way bold is represented
Check the effective font family
Do not assume that the font named in your source is the font used at render time. Check the HTML Text control’s Font property and any inline or generated markup. Test a simple, known-available font against your production choice, one change at a time. Microsoft documents that some fonts do not preserve font weights and styles such as bold and italic in generated PDFs.
Check that a bold face exists
A declaration such as font-weight: 700 asks for a bold face, but the renderer still needs a compatible face for the selected family. Test the same text with the normal weight and with semantic <strong> or <b> markup. If one representation works and another does not, keep the minimal representation that survives your complete pipeline; the documentation does not certify a particular CSS declaration as a universal solution.
Use a controlled test document
Build a small test value containing:
- one paragraph in normal weight;
- the same paragraph in bold;
- a line with punctuation and numbers;
- one long line that can wrap; and
- the exact font family used by the production screen.
Change only the font family, then only the weight markup, and then only the PDF options. Keep each output so you can identify which change altered the result.
4. Inspect the HTML Text control
The HTML Text control renders HTML tags and exposes Font, Size, and padding properties. Microsoft notes that it assumes relatively positioned HTML and that default browser styling for some elements may be removed. Consequently, spacing can originate in the control even when the source string appears correct in a separate browser.
What to inspect
- Look for inherited
letter-spacing,word-spacing,line-height, or transforms in the generated string. - Check whether a parent control supplies a different font or size.
- Remove unnecessary nested spans and inline styles from the test sample.
- Check padding and container dimensions when the apparent spacing is actually a reflow or clipping effect.
Make the smallest reproducible HTML value first. Once its PDF output is stable, add your real markup back in sections.
5. Inspect Rich text editor output
If users enter the content in the Rich text editor, inspect the HTML it emits before conversion. The editor supports bold, but Microsoft says it removes script, style, object, and unsupported HTML elements and attributes. A style you add before or after editing may therefore be removed before the PDF function ever sees it.
A practical pipeline check
- Save one editor entry without modifying it.
- Display the saved HTML in an HTML Text control.
- Inspect whether bold is represented by
<strong>,<b>, an allowed attribute, or plain text. - Compare that display with the PDF.
- Only then add any normalization step, and verify that it does not strip the bold markup.
6. Check native PDF scope and options
For the native function, confirm that you pass the intended screen or supported control. If the symptom includes clipping, unexpected page breaks, or shifted layout as well as spacing, test the documented options separately:
- Paper size: use the target paper size consistently during comparison.
- DPI: test a different value when rasterization or fine text rendering appears different.
- Margins: keep margins fixed while diagnosing font behavior.
- Orientation: keep portrait or landscape unchanged between samples.
- Container expansion: test expansion where supported if content is clipped or a container’s height changes.
These options control document generation and layout; the Microsoft documentation does not establish any of them as a specific cure for bold-font spacing. Generation happens on the device, so device capacity and context belong in a reproducible test report.
Recommended Free Tools
7. A repeatable diagnostic procedure
- Name the route. Record whether the app calls
PDF(...), sends HTML through a flow, or uses a third-party connector. - Create the minimal sample. Use one normal sentence, one bold sentence, and the production font.
- Compare stages. Save a screenshot or observation of the app rendering and the generated PDF.
- Confirm markup. Determine whether the bold is semantic markup or a CSS weight and whether the Rich text editor removed anything.
- Change one variable. Test font family, weight markup, size, and PDF options independently.
- Retest on the affected device. Because native PDF generation runs on the device, include device and app context.
- Document the result. Keep the minimal HTML, effective font, route, options, device, and side-by-side output.
8. Common symptoms, causes, and fixes to test
| Symptom | Likely area | Controlled test |
|---|---|---|
| Bold looks wrong in the app and PDF | HTML, control properties, or editor output | Display minimal HTML, inspect the effective font and markup, and remove extra styles. |
| App looks correct but PDF spacing changes | PDF renderer or font support | Try a known-compatible font and compare semantic bold with a CSS weight. |
| Bold disappears entirely | Font-weight support or stripped markup | Check the Rich text editor output, then test another font and explicit bold markup. |
| Text is clipped or wraps differently | Container size or PDF options | Check margins, DPI, orientation, and supported container expansion independently. |
| Only some devices reproduce it | Device-side generation context | Record device, app version, font, and the smallest sample for escalation. |
9. Native PDF versus connector workflow
Choose based on input scope first. The native function exports current screen or supported-control content and is documented as experimental in the cited Microsoft material. A connector workflow accepts an HTML payload or file according to that connector’s contract and may fit a flow-based document process. Font and CSS fidelity, size limits, licensing, regional support, and operational requirements must be verified for the exact connector and sample; they are not established by the native PDF documentation.
10. When to escalate
Escalate only after you can reproduce the defect with a minimal sample. Include the HTML, the selected font family and weight, the conversion route, PDF options, app and device context, and a side-by-side view of the app and PDF. State whether the issue is incorrect spacing, missing weight, changed wrapping, or clipping. This prevents a renderer problem from being reported as a generic “HTML conversion” failure.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If your goal is a clean image or PDF of a web page rather than a Power Apps screen, ScreenshotNeo provides a one-call website screenshot API. It accepts consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the result with X-Page-Verdict and X-Billed headers. It also offers an MCP server for Claude, Cursor, and other MCP clients, with take_screenshot, get_page_info, and capture_pdf tools.
Use the API documentation at https://screenshotneo.com/docs/ for authentication and options. A cURL request is:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpThe equivalent Python request is:
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)And 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}`);There is a free allowance of 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account to try it.
Best Value
Frequently Asked Questions
Does changing DPI definitely fix bold spacing?
No. DPI is a documented PDF option, but Microsoft does not identify it as a universal fix for bold-font spacing. Test it only as one controlled variable.
Is the Content Conversion connector the same as the Power Apps PDF function?
No. They are different workflows. A plain-text conversion warning from a connector should not be applied directly to native screen-to-PDF output.
What should I send when reporting the issue?
Send the minimal HTML, effective font and weight, conversion route, PDF options, device context, and side-by-side app and PDF output.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
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.
