Cadillac Chrome Obsidian: A Cleaner Chrome to Obsidian Workflow

Cadillac Chrome Obsidian: A Cleaner Chrome to Obsidian Workflow

If you searched for "cadillac chrome obsidian", you might be trying to do one of two things.

Maybe you are researching Cadillac pages in Chrome and want to save them into Obsidian. Or maybe you are collecting pages about Cadillac trims, parts, reviews, financing, manuals, forum posts, or dealer inventory, and you want clean Markdown instead of a messy copy-paste.

I tested this workflow with Web2MD because it solves a very specific problem: turning a page open in Chrome into Markdown that is clean enough for Obsidian, ChatGPT, Claude, Cursor, or any other AI tool.

The important part is that Web2MD runs in your browser. That sounds like a small detail, but it matters a lot when the page is not publicly reachable by a server-side scraper.

The problem with copying Cadillac research from Chrome into Obsidian

Obsidian is great when your notes are plain Markdown. Chrome is great for research. The annoying part is getting web pages from Chrome into Obsidian without dragging along navigation bars, cookie notices, sidebars, random scripts, duplicate links, and broken formatting.

For example, I tested the common manual approach:

1. Open a Cadillac-related page in Chrome
2. Select the main article text
3. Copy it
4. Paste into Obsidian
5. Clean headings, bullets, links, and images by hand

It works, but it is slow. It also fails on pages where the useful content is mixed with menus, comparison widgets, popups, or account-only sections.

For AI use, the problem is even more obvious. If you paste a messy page into ChatGPT or Claude, you waste tokens on junk. If you paste too much, you hit context limits. If you paste too little, the answer misses details.

That is where Web2MD fits.

What Web2MD does

Web2MD is a Chrome extension that converts the current web page into clean Markdown. You can copy the Markdown, save it into Obsidian, or send it to AI tools such as ChatGPT, Claude, and Cursor.

I tested it on typical research pages where someone working on Cadillac notes might spend time:

• Review pages
• Model comparison pages
• Dealer pages
• Owner resources
• Forum threads
• Logged-in pages
• Pages with lots of layout noise

The best result was not that it made everything perfect. No converter does that. The best result was that it gave me a clean starting point in seconds, with the structure of the page preserved.

Here is a simplified example of the kind of Markdown output I expect from a Cadillac model page:

# 2026 Cadillac Escalade Overview

The 2026 Cadillac Escalade is a full-size luxury SUV with three-row seating, advanced driver assistance features, and multiple trim options.

## Key details

- Seating: Up to 7 passengers
- Body style: Full-size SUV
- Notable features: Large display, premium audio, driver assistance
- Common research questions: trims, towing, cargo space, fuel economy

## Notes

Use this page as a reference when comparing Escalade trims or preparing questions for a dealer.

That is the kind of content I want in Obsidian: headings, bullets, and text that can be searched, linked, and summarized later.

Why browser-side conversion matters

A lot of Markdown extraction tools work by sending a URL to a server. That is useful when the page is public. It is less useful when the page requires a login, sits behind a paywall, uses session state, or changes content after the page loads.

This is the main edge of Web2MD.

Because it runs in Chrome, it can convert the page you are actually viewing. If you are logged in and Chrome can render the page, Web2MD can work from that browser context. That is different from asking a remote service to fetch the URL from scratch.

This matters for research workflows like:

• Saving account-only documentation into Obsidian
• Converting pages that require a session cookie
• Capturing a page after filters or search results have loaded
• Working with pages that block bots or server-side readers
• Keeping content local instead of sending the URL to an external scraping API

For a "cadillac chrome obsidian" workflow, that means you can research in Chrome, convert locally, and paste into your Obsidian vault without relying on an outside crawler.

Privacy is a practical feature, not a slogan

I do not think every web page needs a privacy-first workflow. If I am converting a public Wikipedia page, I am not worried about sending the URL to a tool.

But when I am viewing a logged-in page, a quote, a subscription article, a private dashboard, a purchase history page, or internal documentation, I want the conversion to happen locally.

Web2MD is designed for that kind of use. It converts in the browser and does not require an API key for the free tier. That makes it simpler than setting up a developer toolchain, and safer than pasting sensitive URLs into random web converters.

There are still limits. Web2MD is Chrome-only. If you use Firefox, Safari, Arc without Chrome extension support, or a terminal-only workflow, it will not be the best fit. The free tier also gives you 3 conversions per day. If you need more, Pro is $9/mo.

That pricing is reasonable for regular AI research, but it is still a real limit. I would rather say that clearly than pretend the free plan is unlimited.

How it compares with Jina Reader, Firecrawl, and MarkDownload

There are good alternatives.

Jina Reader is excellent for quickly turning public URLs into readable text or Markdown. It is fast, simple, and useful when the page is open to the internet.

Firecrawl is strong for developer workflows. If you need crawling, APIs, extraction at scale, or structured scraping for an app, it is a serious tool.

MarkDownload is a familiar Chrome extension for saving web pages as Markdown, and many Obsidian users already know it.

Where Web2MD wins is narrower but important:

• Browser-side conversion for pages you are already viewing
• Works better for logged-in or paywalled pages than server-side URL fetchers
• Local and private workflow
• Built-in token counter for AI context planning
• One-click send-to-AI
• Free tier with no API key needed

So I would not describe Web2MD as a replacement for every scraping or clipping tool. I would describe it as the tool I reach for when I want the current Chrome page converted into AI-ready Markdown with less friction.

The token counter is more useful than it sounds

The built-in token counter is one of the small features I ended up using more than expected.

When I convert a page, I want to know whether it is small enough to paste into ChatGPT, Claude, or Cursor. If it is too long, I can trim sections before sending it. If it is short, I can include it with a more detailed prompt.

For example, after converting a Cadillac review page, I might prepare a note like this:

# Cadillac CT5 Review Notes

Source: Manufacturer and review research captured from Chrome.

## Summary

The Cadillac CT5 is positioned as a luxury sedan with performance trims, technology features, and a focus on comfort.

## Questions to ask AI

- Compare the CT5 trims in plain English.
- Extract the main pros and cons.
- Turn this into an Obsidian buying guide note.
- Identify details that need verification from the official Cadillac site.

## AI prompt

Use the notes above to create a concise comparison for a buyer who is choosing between luxury sedans.

Before sending that to an AI tool, I can check the token count and avoid guessing. That is especially useful when combining several converted pages into one research prompt.

A simple Chrome to Obsidian workflow

Here is the workflow I would use if I were building an Obsidian vault around Cadillac research:

1. Create an Obsidian folder called Cadillac Research
2. Open a source page in Chrome
3. Use Web2MD to convert the page to Markdown
4. Check the token count if I plan to use it with AI
5. Copy the Markdown into a new Obsidian note
6. Add my own source note, tags, and follow-up questions
7. Send the cleaned Markdown to ChatGPT, Claude, or Cursor if I need summarization or extraction

For internal links, I would keep it simple:

• [[Cadillac Escalade]]
• [[Cadillac CT5]]
• [[Cadillac Lyriq]]
• [[Dealer Questions]]
• [[Ownership Costs]]

The point is not just to archive pages. The point is to make the research usable later.

Where Web2MD is not the right tool

Web2MD is not a full web crawler. If you need to scrape hundreds of pages automatically, Firecrawl or a custom pipeline may be better.

It is also not a replacement for careful source checking. Markdown conversion does not make a page accurate. If you are researching vehicle specs, pricing, or availability, you should still verify details with official Cadillac sources or the dealer.

And because the free plan is limited to 3 conversions per day, heavy daily users will probably need Pro at $9/mo.

Those limits are not dealbreakers for me, but they are worth knowing before you build a workflow around it.

Final take

For the "cadillac chrome obsidian" use case, Web2MD is a practical bridge between Chrome, Obsidian, and AI tools.

It is not trying to be the biggest crawler or the most complex developer API. Its advantage is that it works on the page you already have open in Chrome, including pages that server-side tools may not be able to reach. It keeps the workflow local, gives you clean Markdown, includes a token counter, and lets you move the result into ChatGPT, Claude, Cursor, or Obsidian with less cleanup.

If your current workflow is copy, paste, delete junk, fix headings, then paste again into AI, Web2MD is worth trying.

You can start with the Web2MD Chrome extension and use the free 3 conversions per day to test it on your own Cadillac research pages before deciding whether Pro makes sense.