Are both Autoview Chrome extensions legitimate?

Yes. Both listings are published by the same developer, Autoview Extension Inc. The older one is not a copycat or a scam mirror; it is Autoview's original Manifest V2 build, left published and marked end of life instead of being pulled from the Store.

Why does the old extension have a higher version number than the new one?

Because the version count restarted. When Autoview rebuilt the extension for Manifest V3, the new listing began its own version history at 1.0 instead of continuing the old one. The listing with the bigger-looking version number, 6.122.1, is the one that stopped receiving updates in January 2025. The smaller number, 1.25.1, is the current one.

Will the old Autoview extension stop working?

Google disabled Manifest V2 extensions across all channels of Chrome starting with Chrome 138 in July 2025, so if the old extension is still running for you today, it is likely because you have not updated Chrome recently or a policy override applies. Separately, Google has set August 31, 2026 as the date it removes every remaining Manifest V2 listing from the Chrome Web Store entirely, so even finding the old listing to reinstall it will stop being possible after that date.

Do I need to redo my exchange API keys if I switch to the current extension?

Yes. The two listings are separate installed extensions with separate extension IDs, and Chrome keeps each extension's stored data isolated. Installing the current extension does not carry over keys or settings from the old one; add your exchange connections again after installing.

Does any of this matter if I use the webhook platform instead of an extension?

No. The webhook platform runs on Autoview's servers and does not involve installing anything in Chrome, so the old-versus-new extension question does not apply to it at all.

Which Autoview extension should you install: old vs. new

Autoview · Guide · Updated August 13, 2026

Search the Chrome Web Store for Autoview and two separate listings come back. Same developer, Autoview Extension Inc, on both. Different install counts, different last-updated dates. The version numbers point the wrong way too, if you use them to guess which one is current. This page is the straight comparison, and the short answer up front: install the one below labeled current.

The two listings, side by side

	Current	Legacy
Name	Autoview.com Trading Extension	Autoview
Version	1.25.1	6.122.1
Last updated	June 12, 2026	January 17, 2025
Users	~3,000	~6,000
Rating	3.4 stars (7 ratings)	4.0 stars (78 ratings)
Extension ID	`hjjeplacckkpgfcmgpcnlpmabddkeioi`	`okdhadoplaoehmeldlpakhpekjcpljmb`

The one to install: Autoview.com Trading Extension, ID hjjeplacckkpgfcmgpcnlpmabddkeioi. It's the build this codebase actually ships today, and it's what every current install guide on this site links to. It's also the only extension ID Autoview's own website knows how to hand off to when you connect an exchange through a sign-in flow (more on that below).

The version-number trap

6.122.1 looks newer than 1.25.1. It isn't. When Autoview rebuilt the extension for Chrome's Manifest V3 requirement, the new listing started its own version count over at 1.0 instead of continuing the old one's numbering. The listing with the bigger-looking version number is the one that stopped shipping updates in January 2025. If you're comparing two Autoview listings and picking whichever has the higher version, you're picking wrong.

Why the old listing is already running on borrowed time

The old listing predates Autoview's move to Manifest V3. Autoview's own site material describes it as the original Manifest V2 build, published before Google's V2-to-V3 migration forced every Chrome extension to rebuild or disappear from the Store. Its own description says as much: "This extension version has reached end of life. Upgrading is highly recommended."

That's not just Autoview's call. Google's own Manifest V2 phase-out has a fixed public timeline: Manifest V2 extensions were disabled across every channel of Chrome starting with Chrome 138, in July 2025. If you installed the old Autoview extension before then and haven't touched Chrome's extension settings since, there's a real chance it already stopped running without you noticing. Separately, Google has set August 31, 2026 as the date every remaining Manifest V2 listing gets removed from the Chrome Web Store outright, not just disabled. After that date, the old listing won't be there to find, bookmark or no bookmark.

How to check which one you have

Open chrome://extensions in Chrome, find your Autoview extension, and click Details. Compare the version number and, if you want to be exact, the extension ID in the URL against the table above. A version starting with 1. is current. A version starting with 6. is the old one.

If you're on the old one

Installing the current extension is a separate install, not an update, since these are two different extension IDs to Chrome. That also means nothing carries over automatically: Chrome keeps each extension's stored data isolated from every other extension, old Autoview included. Follow Install the Trading Extension to add the current one, then reconnect your Autoview account and re-add your exchange API keys inside it.

One more reason to make the switch rather than let it slide: Schwab and TradeStation both connect to Autoview through a website sign-in flow, and that flow only knows how to hand the connection off to the current extension's ID. Autoview's website has no code path that opens the old extension for that handoff, so on the old install, that specific connection step has nowhere to go.

Skip the question entirely

None of this applies if you run Autoview through the webhook platform instead of a browser extension. The platform executes on Autoview's servers, nothing to install in Chrome, so there's no old-versus-new extension to keep straight. See how the extension and the platform compare if you're deciding between the two.

Install the current extension