# Render local HTML and CSS

> Browser-only file conversion. Selected files are processed on this device and are not uploaded to a conversion server.

Source: https://localconverter.tech/render-html

Render local HTML and CSS into a PDF or a PNG screenshot using uploaded relative assets. Add the HTML first, followed by the styles, images and fonts it needs, using basenames for asset references. Network access and JavaScript are disabled, making this a static rendering workflow rather than a live website capture.

## Useful tasks

- Render a self-contained HTML report as PDF
- Capture a static HTML layout as PNG
- Preview local CSS with uploaded fonts and images

## Steps

1. **Add HTML before its assets**: Upload the HTML file first, then required CSS, images and fonts. Reference uploaded assets by their basenames so the renderer can resolve the intended local resources.
2. **Choose viewport and output**: Select PDF or PNG and set viewport width and height. These dimensions affect responsive layout, and PNG captures the configured viewport rather than an automatic full-page image.
3. **Render the static document**: Run Process document to render the supplied content with network access and JavaScript disabled. Make sure required text and layout exist without client-side application code.
4. **Inspect layout and asset loading**: Download the result and check fonts, images, responsive breaks and clipped content. For PNG, confirm the intended content fits within the selected viewport height.

## Settings

- **Output**: Choose output according to the result you need. Available choices: PDF; PNG. The initial selection is PDF.
- **Viewport width**: Viewport width accepts values from 320 to 2400, using whole numbers. The initial value is 1280. Change it for a specific output requirement, then check the result before processing more files.
- **Viewport height**: Viewport height accepts values from 200 to 2400, using whole numbers. The initial value is 900. Change it for a specific output requirement, then check the result before processing more files.

## A local report with a stylesheet

A static report.html references report.css and logo.png by basename. Upload the HTML first, followed by both assets, then choose PDF and a suitable viewport width. Inspect the PDF for loaded styles, logo placement and page breaks before sharing the report.

## Check the result

Choose a file, adjust the settings, then download the result. Upload HTML first, followed by relative CSS/image/font assets. Network access and JavaScript are disabled. Asset paths must use uploaded basenames. PNG captures the viewport. Open the saved output in the app or workflow where you plan to use it. Check one representative result before repeating the same settings with more files. The original files stay unchanged.

## Limits

- Uploaded HTML and CSS render to a viewport image. Scripts, images, external URLs, fonts, frames and forms are omitted. CSS support is limited; PDF output is a raster image.
- Files are processed on this device. Browser memory and engine-specific limits apply. Save results before reloading.
- Upload HTML first, followed by relative CSS/image/font assets. Network access and JavaScript are disabled. Asset paths must use uploaded basenames. PNG captures the viewport.
- Upload up to 20 files, at least 1 with a combined size of at most 100 MB. The completed output must fit within 200 MB.
- Files are checked by the local engine; a matching filename alone is not proof of valid contents.
- Selections and completed jobs stay available while you navigate inside this tab. Use My files to revisit results. Reloading or closing the tab clears the workspace; download results you want to keep first.

## Questions

### Can I provide a website URL?

This tool renders uploaded local HTML and its supplied assets rather than fetching a remote website. Network access is disabled, so download or prepare a suitable self-contained static source through your normal workflow before using this renderer.

### Will JavaScript generate the page content?

No. JavaScript is disabled in this rendering workflow. A single-page application that needs scripts to create its content may therefore appear blank or incomplete; prepare static HTML with the necessary content and styles already present.

### How should asset paths be written?

Use the basenames of uploaded files, such as logo.png or report.css, rather than remote URLs or folder paths. Upload the HTML first and its required assets afterward, then inspect the result for missing fonts or images.

### Does PNG include the entire scrollable page?

PNG captures the selected viewport, so content beyond its height is not automatically included in a full-page image. Adjust the viewport within its bounds or choose PDF when the intended document should span rendered pages.

### Does Render local HTML and CSS upload files to another service?

Processing runs in this browser, on your device. Files and pasted input are not uploaded to a conversion server. The website and required engine assets must load first; large operations depend on available device memory.

### Can I continue after changing pages?

Selections and completed jobs stay available while you navigate inside this tab. Use My files to revisit results. Reloading or closing the tab clears the workspace; download results you want to keep first.

## Related guides

- [Merge PDF](https://localconverter.tech/merge-pdf.md)
- [Split PDF](https://localconverter.tech/split-pdf.md)
- [Images to PDF](https://localconverter.tech/images-to-pdf.md)
- [Reorder PDF pages](https://localconverter.tech/reorder-pdf.md)
- [PDF to TXT](https://localconverter.tech/pdf-to-txt.md)
- [PDF to PNG](https://localconverter.tech/pdf-to-png.md)