Sharing HTML

Every browser exports PDF unmarked. Where watermarks actually come from, how to remove the header and footer line, and what to do about a marked file.

Three ways to turn an HTML file into a PDF on macOS, where the Save as PDF option hides in each dialog, and the setting that keeps the colours.

Chrome exports PDF without an extension. What extensions add, what permissions they ask for, and the three cases where one is worth installing.

Why conversion produces a wall of positioned divs, the three routes available, and how to tell in ten seconds whether your PDF can convert at all.

Converting a PDF to HTML with CSS gives you absolute positions, not layout. What is in the generated stylesheet, what to delete, and how to make it reflow.

How to convert Markdown to HTML with a converter, an editor, a build step, or a script. What each route gives you, and how to end up with a readable page.

GitHub Pages converts Markdown to HTML for you through Jekyll. How to switch it on, when to convert the files yourself, and what .nojekyll changes.

Three ways to turn Markdown into HTML in VS Code: the built-in preview, a print-to-HTML extension, and a build task. What each makes, and how to style it.

How to convert HTML to PNG with devtools, a headless browser, html2canvas, or a converter page. Which keeps fonts and charts intact, and what each loses.

How to convert HTML to JPG in a browser, a script, or a converter page. Why text goes fuzzy at low quality, and when PNG is the better choice.

HTML does not convert cleanly to SVG. The foreignObject route, the layout engine route, and when a PNG or a link is the answer instead.

How to turn an HTML page or animation into a GIF: screen recorder, frame capture in a headless browser, and the ffmpeg palette step that fixes colour.

Three ways to turn an HTML page into an MP4: screen recording, browser video capture, and deterministic frame rendering with ffmpeg. Settings that matter.

Three ways to get an HTML page into Figma: an import plugin, pasted SVG, or a flat image. What each keeps as editable layers and what it flattens.

Get a table from a page into Excel. Paste, import, and export routes, and why merged cells and layout tables break all three.

How to generate a Word file from HTML in JavaScript. html-docx-js, the docx builder, and the .doc blob trick, with what each one loses.

Export HTML to PDF from the print dialog, a headless browser, or a library. The print stylesheet rules that stop pages breaking in the wrong place.

Publish your HTML, create a QR code for its link, and test the result. Includes an event-page example you can open, copy, and update without reprinting.

A QR code cannot contain a file. Put the file at an address and encode that, which also means you can replace the file without reprinting.

Turning HTML into a URL takes one paste, not a deployment. What an address actually requires, the four routes compared, and why the file itself is not one.

Online HTML to link tools all return an address. They differ on expiry, on editing later, and on who can open it. How to pick, in one table.

Share a document as a link nobody has to request access to. Why Google Doc links get blocked, what the recipient sees, and when to publish a plain page instead.

Send a Word document as a link instead of a .docx attachment. It opens on a phone, survives mail filters, and the recipient needs nothing installed.

Share a spreadsheet as a link instead of an .xlsx attachment. Figures stay readable on a phone, formulas stay private, and nobody breaks your workbook.

Share a notebook as a link that renders outputs without anyone installing Python. What survives the export, what does not, and when to send the .ipynb.

Share a project with someone who does not use GitHub. What a repository link looks like to a non-developer, and what to send instead.

Share notes with someone outside your organisation. Why OneNote links fail for external recipients, and what to send instead.

Share something so the recipient opens it without signing in. Why drive links ask for access, what a page does differently, and what you give up.

The four ways to share a file online, what each one asks of the recipient, and how to choose. Most of the time the file is not what you are sending.

Reach someone without using email. What works when you have a phone number, a chat, or nothing but a person standing in front of you.

Storage keeps a file. Hosting puts it at an address a reader can open. Which one you need, what each costs, and the questions that decide it.

The three ways to put a document inside a page, which of them fail on a phone, and the fallback that keeps every reader able to open it.

Free image hosts expire, rewrite addresses and add watermarks. What breaks, what to check before relying on one, and when to embed images instead.

A table on a page reads on a phone, keeps its leading zeros and cannot be mangled by the reader. How to build one that stays readable at width.

What actually protects a document, what only looks like it does, and the one control that matters most: being able to take access away.

An expiring link ends access and does not un-send anything. When it is the right tool, when it quietly breaks things, and what to use instead.

The file view shows code and the raw link downloads it. Neither renders the page. What actually publishes it and what to watch for.

Print styles decide what appears on paper. The twenty lines that hide the furniture, keep tables whole and make links useful once printed.

Every collaboration tool assumes the other person signs in. What to do when they are a client, a supplier or somebody who will not create another login.

An archive of pages becomes a site when the folder structure and the paths agree. What has to be at the root, and the path mistake that breaks everything.

Converting a design image to a working page means rebuilding it as text. What the automatic tools produce, and why the text has to be real.

A file on your machine is already a page. What it is missing is an address, and the four things that have to be true before it works for anyone else.

Uploading is the easy part. What decides whether the result works is the file name, the paths, and what the service does to the address afterwards.

Hosting is replaceable and the address is not. What a domain costs, what it protects, and the two records that point it at a page.

Calculators, converters and internal tools do not need a server. Where the line is, and what to do about the three things that cross it.

The file works on your machine and arrives as code for everyone else. What to check before sending, and what to write alongside the link.

A build produces a folder of static files. What has to be configured for routing to work, and the base path mistake that breaks every asset.

Serving the same content at three addresses splits your links and confuses search. Pick one, redirect the rest, and keep the extras anyway.

Serving the file is easy. Whether another site can read it depends on one header, and whether it is safe depends on what is in it.

A shared stylesheet is a dependency for every page that loads it. Caching, paths inside it, and why editing one changes several sites at once.

A script at an address runs with full access to every page loading it. Caching, content type, and what you take on by sharing one.

A vector image can contain scripts, which is why some hosts refuse to serve one inline. What to strip, and when to inline it instead.

Self-hosting a typeface removes a third-party request and introduces two new problems: licensing and the moment before it loads.

A page with no icon gets a blank square in every tab and bookmark. Three files cover every place one is used, and caching hides your changes.

Storage is for finding things again. Naming, folder depth and what to do about the versions problem, before it becomes forty files called final.

Automatic conversion reproduces the appearance with absolute positioning that breaks at every other width. What the real work is.

Once something fetches your file, the address and its shape are a contract. What to version, what to cache, and what never to change.

The tool exports a folder of tiles and a page. What has to stay together, why the tile count is large, and the path mistake that breaks it.

Permanence, privacy, whether it displays, whether it can be corrected, and whether you learn it was opened. Every document link answers all five.

Converters turn a fixed page into absolutely positioned markup that breaks on a phone. When conversion is the right answer and when publishing is.