Skip to main content

md2linkedin

PyPI version Python versions

md2linkedin converts Markdown text to LinkedIn-compatible plain text by replacing bold, italic, and bold-italic markers with Unicode Mathematical Sans-Serif characters. This preserves visual formatting when pasting into platforms like LinkedIn that do not support Markdown natively.

Installation

uv add md2linkedin

Tip: Run the CLI without installing it with uvx md2linkedin post.md.

Usage

Python API

# @pyodide
from md2linkedin import convert

md = """
# Exciting News

I'm thrilled to share that **we just launched** a new product!

Key highlights:

- **Performance**: *3x faster* than the previous version
- **Reliability**: ***zero downtime*** deployments
- **Developer UX**: clean, intuitive API

Check it out and let me know what you think.
"""

print(convert(md))
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
𝗘𝗫𝗖𝗜𝗧𝗜𝗡𝗚 𝗡𝗘𝗪𝗦
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

I'm thrilled to share that 𝘄𝗲 𝗷𝘂𝘀𝘁 𝗹𝗮𝘂𝗻𝗰𝗵𝗲𝗱 a new product!

Key highlights:

• 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲: 3𝘹 𝘧𝘢𝘴𝘵𝘦𝘳 than the previous version
• 𝗥𝗲𝗹𝗶𝗮𝗯𝗶𝗹𝗶𝘁𝘆: 𝙯𝙚𝙧𝙤 𝙙𝙤𝙬𝙣𝙩𝙞𝙢𝙚 deployments
• 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝗨𝗫: clean, intuitive API

Check it out and let me know what you think.

CLI

# Convert a Markdown file (output: post.linkedin.txt)
md2linkedin post.md

# Specify output path
md2linkedin post.md -o linkedin_post.txt

# Pipe from stdin
echo "**Hello**, *world*!" | md2linkedin

# Keep link URLs in the output
md2linkedin post.md --preserve-links

# Disable monospace code rendering
md2linkedin post.md --no-monospace-code

Key Features

  • Bold: **text** or __text__ → Unicode Sans-Serif Bold (𝗯𝗼𝗹𝗱)
  • Italic: *text* or _text_ → Unicode Sans-Serif Italic (𝘪𝘵𝘢𝘭𝘪𝘤)
  • Bold-italic: ***text*** or ___text___ → Unicode Sans-Serif Bold Italic (𝙗𝙤𝙡𝙙-𝙞𝙩𝙖𝙡𝙞𝙘)
  • Headers: #/##/etc. styled with bold Unicode; H1 gets a ━ border
  • Code spans: backticks stripped, content rendered in Unicode Monospace (𝚌𝚘𝚍𝚎) by default; --no-monospace-code keeps plain text
  • Fenced and indented code blocks: fences and indent stripped, content rendered in Unicode Monospace by default; --no-monospace-code keeps plain text
  • Links: stripped to display text by default; --preserve-links retains URLs
  • Images: replaced by alt text
  • Bullet lists: -/*/+ → •; nested items get one marker per level (‣, ◦, ▪)
  • Ordered lists: numbers kept verbatim, counting on from wherever the list starts
  • Tables: header row in bold, cells joined by |
  • Strikethrough: ~~text~~ → text, markers dropped
  • Blockquotes: leading > stripped at every level of nesting
  • HTML spans: unwrapped, inner text preserved
  • HTML entities: decoded (& → &, etc.)
  • Backslash escapes: resolved (\* → *)
  • Windows line endings: normalised automatically
  • Emojis & non-ASCII: pass through unchanged — no accidental corruption

Limitations

Converting Markdown to LinkedIn-friendly text relies on Unicode Mathematical Alphanumeric Symbols to simulate styling. This approach has notable limitations:

  • Code Blocks: Monospace Unicode characters do not enforce true fixed-width alignment on proportional fonts (like LinkedIn's default font). As a result, indentation and column alignment in code blocks will often break visually.
  • Tables: Markdown tables are flattened to one line per row, with a bold header and cells joined by |. Nothing keeps the columns aligned on LinkedIn's proportional font, so wide tables are better rewritten as lists.
  • Accessibility: Screen readers often read Unicode mathematical characters aloud individually (e.g., "mathematical sans-serif bold b") instead of as complete words, making the content difficult for visually impaired users to understand.
  • Searchability: Text styled with these Unicode characters may not be indexed properly by LinkedIn's search algorithm, meaning people searching for your keywords might not find your post.
  • Markdown extensions: The converter reads CommonMark, plus tables, strikethrough and autolinks. Task-list checkboxes and footnotes are not enabled, because LinkedIn has nowhere to put them: - [ ] todo keeps its literal [ ], and text[^1] becomes text^1. See What Gets Transformed for the full list.

For more examples, check out the package documentation at: https://www.indrapatil.com/md2linkedin/

See Also

License

This project is licensed under the MIT License.

Code of Conduct

Please note that the md2linkedin project is released with a Contributor Code of Conduct. By contributing to this project, you agree to abide by its terms.

Acknowledgements

Hex sticker font is Rubik. Icons are sourced from Flaticon:

Metadata

Release files for md2linkedin 0.5.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for md2linkedin 0.5.0
File Size Uploaded
md2linkedin-0.5.0.tar.gz 14.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for md2linkedin 0.5.0
File Interpreter ABI Platform
md2linkedin-0.5.0-py3-none-any.whl Python 3 none any Details

Total release size: 28.6 kB

Release files / md2linkedin-0.5.0.tar.gz

Download URL md2linkedin-0.5.0.tar.gz
Size 14.1 kB
Tags Source
SHA-256 checksum
How to use checksums
4945c6b462b80f4065a0b0f58f1603760d0a7b9109ceb62ad0dda35496d263be
BLAKE2b-256 checksum
How to use checksums
14c3f3adaa5f8b5b552cf569494d47e2b863d599355be47fbe5a19cbd8e3d775
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 7, 2026.

Transparency log

Release files / md2linkedin-0.5.0-py3-none-any.whl

Download URL md2linkedin-0.5.0-py3-none-any.whl
Size 14.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a50f83f03c70880674ff2edbb417d63b3d4ce692ba86d90e7ad5d6264a2a5431
BLAKE2b-256 checksum
How to use checksums
e27b9b6ce9ae35a8041fa78d6e941856015dc2ab84c4d4d08b832d1719035470
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 7, 2026.

Transparency log

Release history Release notifications | RSS feed

0.5.1

2 release files

This release

0.5.0 This release

2 release files

0.4.0

2 release files

0.3.0

2 release files

0.2.3

2 release files

0.2.2

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page