Use IntelliJ IDEA’s View | Open in Browser command to render an HTML page. Select Built-in Preview for an editor tab, or choose a configured external browser. The built-in preview is served by IntelliJ IDEA’s web server (default port 63342) and normally reloads when you save HTML, CSS or JavaScript. For an actual screenshot, use your operating system’s capture utility: IntelliJ IDEA’s Full Screen and Presentation modes change the view but are not documented as screenshot commands. If you need source code as a static, shareable HTML document instead of a running page, use File | Export | Files or Selection to HTML….
Choose the workflow that matches what you mean
“Render HTML/CSS” and “take a screenshot” are separate jobs. Rendering runs the page so you can inspect layout and behavior. A screenshot records the pixels currently visible on screen. Exporting code to HTML creates a formatted, static listing rather than running the application.
| Goal | IntelliJ IDEA workflow | Output | Automatic updates | Debugging required? |
|---|---|---|---|---|
| See a web page | View | Open in Browser | Interactive page in Built-in Preview or an external browser | Reload on save by default; configurable | No |
| See CSS and JavaScript changes without a full reload | Live Edit while debugging | Updated page in a supported Chromium-based browser | Live updates, with a documented 300 ms default delay | Yes |
| Publish a code listing | File | Export | Files or Selection to HTML… | Static HTML with syntax highlighting and indentation | No; export again after edits | No |
| Capture what is visible | Your operating system’s screenshot utility | Image of the current screen or selected region | No | No |
How do I preview HTML in IntelliJ IDEA?
Open the page in Built-in Preview
- Open the project containing your HTML file.
- Open the HTML file in the editor.
- Select View | Open in Browser.
- Choose Built-in Preview. IntelliJ IDEA opens the rendered page in an editor tab.
The built-in preview uses IntelliJ IDEA’s built-in web server, which JetBrains documents as always running and requiring no manual server setup. Its documented default port is 63342 in the current IntelliJ IDEA 2026.2 help. The preview resolves linked stylesheets and scripts through that server, so relative paths should be written as they are in the project.
Open the same page in an external browser
Use View | Open in Browser again and select a configured browser. This is useful when you need to compare Chromium, Firefox or another installed browser, inspect responsive behavior with that browser’s developer tools, or reproduce a browser-specific issue. The page is still opened through IntelliJ IDEA’s local web server unless you deliberately configure another server.
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 →Control reload behavior
Open Settings | Tools | Web Browsers and Preview. IntelliJ IDEA’s current settings expose reload choices including On Change and Disabled; the normal workflow reloads after a file is saved. Use On Change when you want edits reflected as soon as the IDE detects them, or Disabled when a reload would reset application state.
Automatic reload does not work when the page has been uploaded to a manually configured default web server. In that case, refresh through the server or configure the project to use the built-in preview during development.
How do I see my CSS changes live?
Use ordinary preview for save-and-reload
For most static pages, edit the CSS file, save it, and let Built-in Preview reload. This is the simplest path because it does not require a debugging session or additional plugins.
Use Live Edit for debugging-time updates
Live Edit is a different workflow: it applies supported HTML, CSS and JavaScript changes while you debug the page. JetBrains documents these prerequisites:
Recommended Free Tools
Rank #2
- The bundled JavaScript and TypeScript plugin.
- The JavaScript Debugger and Live Edit plugins.
- An IntelliJ IDEA edition and subscription that provide those plugins; JetBrains states that the two plugins are available only with an IntelliJ IDEA Ultimate subscription.
- Chrome or another Chromium-based browser for JavaScript debugging.
- Confirm the required plugins are enabled in Settings | Plugins.
- Open the HTML page through View | Open in Browser in a supported Chromium-based browser.
- Start a JavaScript debugging session using the IDE’s browser-debug configuration.
- Edit HTML, CSS or JavaScript. Live Edit applies compatible changes while the session is active.
The documented default Live Edit update delay is 300 ms. Live Edit is not a synonym for preview: it depends on debugging, browser support and edition/plugin availability. If your edition does not provide the required plugins, use save-and-reload preview instead.
How can I export code to HTML in IntelliJ IDEA?
Use this workflow when the recipient needs to read your source, not execute your web application.
- Select File | Export | Files or Selection to HTML….
- Choose the files or selection to export and set the destination.
- In the export dialog, enable any presentation options you need, such as line numbers, hyperlinks to classes or opening the generated file in a browser.
- Complete the export and share the generated HTML.
The result is static HTML that preserves syntax highlighting, indentation and source structure. It does not run your page, load application data, execute JavaScript or prove that the exported files work together in a browser. Export again after source changes because the output is a snapshot of the code at export time.
What about Markdown preview?
Markdown has its own editor preview that renders Markdown as HTML in a live preview pane. Its settings can load a custom stylesheet or accept custom CSS rules. That preview is intended for Markdown documents; it is not a replacement for running an HTML application with its scripts, routes and assets.
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 matchHow do I take a screenshot of my IDE or rendered page?
Capture the rendered page
- Open the page in Built-in Preview or your chosen external browser.
- Resize the IDE or browser so the exact region you want is visible.
- Use your operating system’s screenshot utility to capture the full screen, a window or a selected region.
- Save the image in the format required by your documentation, issue tracker or design review.
Capture the IDE itself
Switch to the editor, tool window or layout you want, then use the operating system capture utility. IntelliJ IDEA’s Full Screen and Presentation viewing modes can remove distractions or enlarge content, but the official documentation found for current IntelliJ IDEA does not describe either mode as a general screenshot feature. Do not confuse changing the view with saving an image.
Prepare a reliable capture
- Wait for fonts, images and asynchronous content to finish loading before capturing.
- Use the same browser zoom and window dimensions when comparing revisions.
- Capture the browser’s rendered page, not the HTML source, when documenting visual output.
- If a page extends beyond the viewport, use a browser’s full-page capture facility or an image tool that supports scrolling; an ordinary OS capture records only visible pixels.
Preview, export or screenshot: a practical decision guide
- Interactive layout check: Built-in Preview or an external browser.
- CSS iteration without a debugger: Save and reload with the reload setting left enabled.
- Instant debugger-linked edits: Live Edit, if your edition, plugins and browser meet JetBrains’ requirements.
- Code review or a documentation appendix: Export to HTML.
- Evidence of what a person saw: An operating-system screenshot of the rendered page.
Troubleshooting common IntelliJ IDEA problems
The browser option is missing
Check that an HTML file is open and that you are using View | Open in Browser. Then review browser entries in Settings | Tools | Web Browsers and Preview. Product editions, plugins and version-specific UI can change which actions appear.
The page opens, but CSS or JavaScript is missing
Inspect relative paths and file names, including letter case. Open the page through the IDE action rather than as a raw file:// URL, then inspect the browser developer console for failed resource requests. A stylesheet or script that is outside the served project path may not be available to the preview.
Changes are not appearing
Save the edited file and check the reload setting in Settings | Tools | Web Browsers and Preview. If it is Disabled, refresh manually. If the page is being served by a manually configured default web server, IntelliJ IDEA’s automatic reload behavior does not apply.
Live Edit does nothing
Live Edit requires an active debugging session, the JavaScript and TypeScript bundled plugin, the JavaScript Debugger and Live Edit plugins, and a supported Chromium-based browser. Confirm that your IntelliJ IDEA edition and subscription include the plugins. For a simple static page, stop debugging and return to save-and-reload preview.
The preview cannot be reached on the expected port
The documented default built-in-server port is 63342. Check the server and browser settings, any project-specific configuration, and local security software that could block access. Do not assume another machine can reach your local preview: treat it as a development endpoint and use the IDE’s documented external-access settings when remote access is genuinely required.
The screenshot is blank or incomplete
First verify that the page itself has finished loading and that images, fonts and scripts work in the browser. A screenshot utility cannot capture content that has not rendered. For content below the viewport, use a full-page browser capture rather than a normal visible-region screenshot.
The exported HTML looks right but the application is broken
That is expected when the goal was source export. Export to HTML produces a static, formatted code listing; it is not a deployment bundle or a running application. Use Built-in Preview or an external browser to test behavior.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Best Value
Or skip the browser setup
When a page is available at a URL, ScreenshotNeo can render it through one request. Before capture, it accepts cookie or consent banners and removes more than 60 known consent platforms, newsletter popups and chat widgets; each cleanup step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed, and each response reports the result with X-Page-Verdict and X-Billed headers.
See the ScreenshotNeo API documentation for the full parameter list. This cURL example saves a WebP image:
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}`);Replace the example URL with the page you need to capture. ScreenshotNeo also provides an MCP server for AI agents, including Claude, Cursor and other MCP clients, with take_screenshot, get_page_info and capture_pdf tools.
Capture options relevant to rendered HTML/CSS
- Full-page capture with lazy-loaded images.
- Capture one element by CSS selector.
- Dark mode, 12 device presets, arbitrary viewports and retina scale.
- PNG, JPEG or WebP output, plus PDF with paper size, margins, landscape mode and page ranges.
- HTML/CSS-to-image rendering, custom CSS and JavaScript, and clicking an element before capture.
- Hide selectors; wait for a selector, a delay or network idle.
- Block ads, trackers, requests or resource types.
- Custom headers, cookies, user agent and Authorization values.
- Timezone and geolocation controls, transparent backgrounds and image resizing.
- Caching with a TTL you choose, signed links for public
<img>tags, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, a usage API and an OpenAPI specification. - Parameter names used by other screenshot APIs also work, which can simplify a migration.
Plans and billing
| Plan | Price | Included shots |
|---|---|---|
| Free | $0 | 1,000 per month; no card |
| Starter | $5 | 3,000 |
| Growth | $15 | 15,000 |
| Pro | $39 | 60,000 |
| Scale | $99 | 250,000 |
| Business | $249 | 1,000,000 |
Every feature is included on every plan, and yearly billing gives two months free. The free plan includes 1,000 screenshots each month without a payment card. Create a free ScreenshotNeo account to get started.
Reliability and workflow notes
For local development, IntelliJ IDEA’s built-in server keeps the feedback loop short because there is no separate server installation to maintain. For repeatable documentation, CI jobs or captures from multiple devices, an HTTP screenshot API avoids depending on one developer’s screen size and desktop state. Keep the distinction clear: IntelliJ preview helps you inspect a page interactively; an API returns an image or PDF that can be stored, tested or embedded.
Frequently Asked Questions
Can I use IntelliJ IDEA’s export command to create a deployable website?
No. Files or Selection to HTML creates a static, syntax-highlighted representation of source code. Use the browser preview or your normal web build and deployment process for an executable site.
Why can two screenshots of the same page differ?
The visible result can change with viewport dimensions, browser engine, zoom, device pixel ratio, loading state and dynamic content. Keep those conditions consistent when comparing captures.
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.
Free tools Windows power users keep installed
One-click scans. No signup required.
