Dec 042014

A some may be already aware of, Google has announced that it will phase out support for NPAPI in Chrome with the ultimate removal in Sept 2015.   We use NPAPI in the framework for plugin support for most browsers except for IE which we use an ActiveX plugin.  We are investigating alternatives to NPAPI but we have not come up with a solution yet.

In the mean time before Sept 2015, you will have to possibly change several settings in your Chrome browser in order to use the DYMO Label Framework:

  1. Click on the Chrome Customize button in the upper right of your browser
  2. Find the Settings option
  3. Click on the “Show Advanced Options” link
  4. Click on the “Content Settings” button or browse to chrome://settings/content
  5. Verify that “Allow all sites to run JavaScript” is enabled
  6. Verify that under Plug-ins that “Run Automatically” is selected
    1. You can check in the “Plug-in exceptions” to see if the site you are running the Framework from is set to “Allow” instead of “Block”
  7. Verify that “Unsandboxed plug-in access” is not set to “Do not allow any sites….”



This should get things working.

Another work around, though less than ideal is to use the extension IE Tab.  This will put a web page into an IE browser tab within Chrome and will use the ActiveX plugin instead of the NPAPI version.  It has options to add a wild card URL that will automatically use the IE Tab when it matches.  We recognize that this is not a valid long term solution.

Update (4/15/2015)
With version 42 of Chrome, Google now disables NPAPI which is required to run our plugin. However, you can manually enable it by typing the following into the Chrome address bar and adjusting the setting:

Update (4/20/2015)
It has been our experience that just enabling NPAPI may not be enough. In some instances, close the chrome browser then uninstall and re-install the DLS software for the plugin to appear in the plugin list: chrome://plugins/
Go here to see if your browser has the framework installed correctly: Check Environement

Update (5/8/2015)
In some situations, a full shutdown and reboot is required after all the steps have been performed for the plugin to appear in Chrome.

  205 Responses to “DYMO Label Framework and Chrome”

  1. Thanks for the info and for the workaround! It’s such a drag that Chrome is doing this :(

  2. Despite setting Chrome preferences as shown, I am unable to print from a web application to labelwriter 450 turbo. In fact, installation of DLS (latest version) on a machine running windows 8 fails to install the label framework plugin. Here is the output of

    isBrowserSupported: true
    isFrameworkInstalled: false
    errorDetails: DYMO Label Framework Plugin is not installed

    Any suggestion would be heartily welcome.

    • I have sent you an email to you to provide all steps and screens to make plugin working in chrome.

    • I’m having the same issue. Does anyone have a fix already? #HALP!

    • I’m seeing this issue also. I would love the email to get things working also. [email protected]

      • We’ve update this post with more explicit directions. You’ll want to make sure that your Chrome browser is closed before re-installing DLS and for more step by step directions there is a post by “pi” in this thread that has that information.

        • I’m having the same issue. I’m not a developer. Following the instructions that were updated 3 days ago I checked my environment and get the following result
          isBrowserSupported: true
          isFrameworkInstalled: false
          errorDetails: DYMO Label Framework Plugin is not installed

          Silly question is DLS = dymo label software? should I just try reinstall that?

          • Hi Shelly, yes DLS is referring to the DYMO Label Software. Make sure you follow the steps and that Chrome is closed before you re-install DLS.

    • I am getting this message
      errorDetails: Unable to create DYMO.Label.Framework ActiveX object. Check that DYMO.Label.Framework is installed. Exception details: Error: Automation server can’t create object
      How can I fix. I am running windows 8 – 62bit
      Wont work on chrome or explorer

  3. Ouch, very troubling news. Chrome is the most popular browser among our users and telling them to switch to Firefox is not going to go over very well, IE Tab is not an option for us. The DYMO Label Framework has been perfect for our use, please keep us informed, hopefully you can get it straightened out.

  4. Yikes!

    I have over 1000 customers that use Dymo label printers using the this. They absolutely love it.

    Another hardware device my customers use was facing the same hurdle. What they did was create some sort of windows software that listens over an http socket on localhost. Then the javascript library makes ajax calls to send and pull data back and forth. Saved them from having to write extensions for all browsers.

  5. With all of these settings enabled, the plugin is still not working on Chrome.
    isFrameworkInstalled: false, errorDetails: “DYMO Label Framework Plugin is not installed”

    Is there anything that can be done to get the plugin to work on Chrome?
    I am using Version 39.0.2171.99 m

    • Are you using a 64-bit version of Chrome? We’ve noticed issues with the plugin and 64-bit Chrome recently.

      • No, I am using the 32 bit version of chrome. And I am not receiving any prompt to enable the plugin.

      • Is there any solution to get this working on 32 bit chrome?
        I can get it to work on Firefox, but I am using other HTML 5 features which do not work on Firefox, so I need this on chrome.

  6. Still awaiting a response if there is some way to get this to work on Chrome.

  7. We really need this to work for Chrome. Are you working on a version that fully supports Chrome?

    • To work with chrome, go to chrome://plugins/ and enable DYMO Label Framework Plugin (DYMO Label Framework – Version: Pls make sure you have latest DLS installed before you do that.

  8. Since your comment system doesn’t want me to post links on the subject, I’ve added a single link to a pastebin to my lectures about NPAPI end-of-support in major web browsers, and possible solutions.

    Hope it help.

  9. Hoping someone can shed some light on how the search for an alternate solution is going. Has anything been identified yet for support in a post NPAPI world? Response greatly appreciated as users are beginning to ask what will happen in September when NPAPI no longer works in Chrome.

    • Bryan,

      We think we have identified an alternate solution and are in the initial stages of development. We understand the urgency on this but we want to ensure that when we release a fix, it is not just a stopgap solution and is something that will work for the foreseeable future. I don’t have too much to share on when we will release the solution but I can say it will be at least a few months.

  10. If you would open source this we could all help out – this feature is a hugely useful tool and one that could be taken much further if the community was given the chance to help.

    It would be great free marketing as currently no one really knows about this Dymo capability, you’re not getting much competitive advantage for a rarely updated, un-marketed feature – this site it impossible to find from visiting and this blog is rarely updated and not prominent in search engine results and the examples barely scratch what can be done with this.

    Let the code be free, put it on Github, start accepting pull requests and the community will sell it for you.

    • I think Ben’s idea is great and would be interested in submitting some PR and helping resolve the NPAPI issues, especially as DYMO doesn’t work with 64bit chrome.

  11. Chrome 42 was released today, and so your printers no longer work in Chrome.

    Please let us know if we can help with getting this fixed as if it doesn’t it means we will have to start recommending other printers to our customers.

    • I am not able to duplicate the issue with Chrome 42 running the following sample:

      It prints just fine. Please make sure all the settings mentioned above have been changed.

      • Hi Pi,

        Yep, the settings are exactly the same as you’ve mentioned above, it worked with version 41 but not with version 42. The google NPAPI article says that NPAPI is now disabled.

        Like Marvin we have hundreds of users (most non-technical), as such the above solution is not workable. When we have so many non-technical users all around the world our only real solution is to suggest they use another web browsers, even this is stretch for some.

        If we are going to continue to support your hardware we need to know that you have a plan and what the timeline is, if you can’t share something then frankly we wont be able to continue to support your hardware.

  12. We have also started experiencing issues today. Starting Chrome 42 the Dymo plugin stops working. After manually enabling the NPAPI it works again but we have more then 500 installations of this at the moment, can’t really ask all of them to go deep into Chrome settings to change this. Plus, this is only a temporary fix untill final deprecation in September. Dymo, please shed some light on the roadmap for a future solution!

    • It should be possible to programmatically update the chrome settings.

      Currently we are working on a solution which should be ready before September.

  13. We just upgrade to Chrome 42 and the printing piece has stopped working as well. I’ve tried the workaround steps above and it hasn’t made a difference.

    We get “Is Framework Installed: false” and “DYMO Label Framework Plugin is not installed”. Chrome does not prompt us to allow add-on and the plugin isn’t listed in our settings.

    Any suggestions?


  14. Dymo javascript framework is also broken for us on Firefox because our web app directly uses your source:

    That source is no longer there. Can you get it back asap? Thanks!!!

  15. Thanks for the 4-15-15 workaround; worked wonderfully!! Your support is very much appreciated.

  16. Hi,

    The file became unavailebla. Has anyone an idea where to find an copy of the file, or if anyone has an local copy that would be great.

    Thanks in advance

  17. I find it rather troubling that this NPAPI issue has been known for at least 18 months and the talk is that it SHOULD be fixed by September… I mean this had to have come up in meetings at least a few times, someone dropped the ball on addressing this issue.

    Ahh well, maybe a 5000% increase in support ticket volume will make senior management realize that this should be fixed…

  18. This workaround works for me. However, come September when Chrome kills NPAPI support entirely does this mean Dymo will no longer work in Chrome?

    Do you folks have plans to get this working with a more secure type of plugin such as PPAPI that will still be supported?

    Any info would be appreciated. Thanks.

    • We have researched PPAPI. Unfortunately PPAPI doesn’t support what we need!

      We are pursuing a different solution and the goal is to have a solution by September.

      • As I understand PPAPI does not have USB support yet, though Chrome APP’s do have.
        Wouldn’t it be possible to port existing libraries to PPAPI and perform communications with USBthrough an APP?
        This way it would be an APPwith full support for all printer functions across multiple platforms, including even chromeos.

        And it would be possible to communicate with APPusing messaging api from both extensions and webpages (though this would need an app to block any requests until source approved, i.e. settings page with list of message sources and their access state)

        • Anton,

          This approach may work, but we have identified an alternate approach that we are currently working on.

  19. Just a tip: after hitting chrome://flags/#enable-npapi and enabeling NPAPI in Chrome 42 it is nessesary to close the browser and restart it, then the Dymo printer should become available again.

    I support the open source suggestion btw!

  20. DYMO – I agree that I’m a bit nervous with September being so close. I appreciate you responding to comments on this post notifying us of a solution that’s coming but the vagueness of the replies worries me. The lack of transparency makes me concerned that your confidence in the solution is low. Are there any additional details you’re able to provide?

    Everyone Else – It sounds like we’re all pretty concerned about September and we’d all like to know our options. While I really appreciate the solution DYMO has supplied over the past years, we need to do what’s best for our companies. Is anyone aware of any alternatives to DYMO that provide a smooth web integration that won’t be subject to the NPAPI updates?

    • Hi Jonathan,

      I understand your concerns and you need to do what is right for your companies. As a sign of some transparency, we have researched and tried various solutions. NaCL, PNaCL and Native Messaging Host are some of the solutions that we researched. None of them were viable as a NPAPI replacement for us for various reasons. The most promising was using Native Messaging Host. This actually works if we wanted to build a Chrome labeling plug-in but it does not work for providing a label API that could be used by third parties due to domain restrictions. Our current solution centers around using services and this could potentially replace all plugin’s. In the end, we want to provide a thought out and solid solution that is not rushed into.

      We thank you for being our customer and appreciate your patience.

      • Thanks for the reply and I really appreciate you responding. I can also appreciate wanting to get the implementation right and I’m sure you’re feeling plenty of the stress with the September deadline. We’ll hang in here and if there’s anything the community can do (open source it, beta testing, etc) I’m sure plenty of us would be willing to help. I think most of us are here because no one else is doing what you are with web-based label printing and we love it.

  21. ListLabelShip has sent me instructions on how to enable the Dymo Label Framework plugin. The problem is, it isn’t listed at all anymore under plugins. I can’t enable it manually because it has vanished, and re-installing the software for my LabelWriter 450 doesn’t help. Any solutions?

    • First make sure that you have enabled NPAPI (chrome://flags/#enable-npapi). Then follow the steps in the post above in order to enable the DYMO Label Framework.

      If the DYMO plugin still doesn’t show up (chrome://plugins/) then you might have to uninstall and re-install DLS.

      • I have uninstalled and re-installed DLS and the Label Framework plugin still does not come up.

        • Please make sure to enable NPAPI first and also follow the steps mentioned in post above.

          What does the following link return?

          • It says that Label Framework is not installed. I uninstalled the software and tried to re-install it (3 times.) When it gets to where I connect the printer and it completes the printer installation nothing happens, so I cannot finish the installation. Do you know what is wrong? It is not installed right now.

          • Please try the following:
            1. Uninstall DYMO Label Software (DLS)
            2. Install Chrome 42 if it isn’t installed yet
            3. Enable NPAPI by typing the following into the Chrome address bar: chrome://flags/#enable-npapi
            4. Close Chrome
            5. Install latest DLS 8.5.1
            6. Launch DLS and make sure you can print a label
            7. Close DLS
            8. Launch Chrome
            9. Click on the Chrome Customize button in the upper right of your browser
            10. Find the Settings option
            11. Click on the “Show Advanced Options” link
            12. Click on the “Content Settings” button or browse to chrome://settings/content
            13. Verify that “Allow all sites to run JavaScript” is enabled
            14. Verify that under Plug-ins that “Run Automatically” is selected
            1. You can check in the “Plug-in exceptions” to see if the site you are running the Framework from is set to “Allow” instead of “Block”
            15. Verify that “Unsandboxed plug-in access” is not set to “Do not allow any sites….”
            16. Restart Chrome
            17. Verify that the DYMO Label Framework plugin appears in the plugin list: chrome://plugins/
            18. Make sure the framework in installed correctly:
            19. Print a label with the following sample app:

  22. hi, the system won’t let me print any label after the newest update of window. I’d follow every step and it doesn’t seems it work for me. do you guys have any solution?

    • With version 42 of Chrome, Google now disables NPAPI which is required to run our plugin. I don’t have an issue with Chrome 42 once I have enabled the NPAPI again.
      You can manually enable it by typing the following into the Chrome address bar and adjusting the setting:

      If it still does not work then you have to reinstall DLS.

  23. The only fix that has worked for us is installing an older version of Chrome and disabling all updates through the Windows register. Not safe, but the only way to print hundreds of shippinglabels today.

  24. So just so I understand, come September 2015, this plugin will no longer work in Chrome. You guys (DYMO) are currently investigating a fix/resolution to that problem. How will you notify the community of us users when the fix or workaround becomes available? Thanks for your help and your replies!

    • Hi Frank,
      That is correct, we are working on the problem and will inform the community through this blog when we reach a Beta stage and again when we release into production. That being said, when we hit the Beta stage, we would like to engage the community to help us test.

      Thank you again for your patience!

  25. Hi,
    Just another concerned customer.
    Our company uses a lot of Dymo printers, and the plugin to print labels.
    Hope you can develop another solution to print using Chrome, and updated, when time comes. Or we will need to switch all our printers.
    We don’t want to not update the browser, due to the obvious security reasons.

    • Hi Pedro,

      We do hope our solution will satisfy your requirements and we’ll keep you informed of our progress.

      We appreciate your patience in this matter.

      • I’m still worrying about not having a solution in time.
        And until september, in every update, i need to go to the flags and enable npapi.

        Chatting with some friends, and doing a quick research only. Not sure about the viability, but i think we have a few options.
        Hvae you thought about node.js? or creating and app/extension for chrome and firefox? theres is also chrome.printerProvider in dev, but maybe useful.

        The sooner you release a solution, the better. Only then can i rest my mind about this issue.

        • Hi Pedro, We have done a lot of research into this and unfortunately none of the mentioned solutions are a suitable replacement to NPAPI. We are actively working on the solution and will present more information about it soon. Thank you for your patience.

  26. Hi,

    I’ve tried every step here a few times, uninstalled and reinstalled, checked plugins etc. It isn’t appearing in the plugins in chrome, nor is the framework supported.

    I’ve checked every javascript permission and tried everything offered. No joy. Can you please advise?

    • Hi Martha,
      If you have followed all the steps, from enabling chrome://flags/#enable-npapi, closing chrome and then re-installing DLS after that, this should work. We have not been able to reproduce a situation where the steps we provided did not work. The only other suggestion we have is to revert your browser version and turn off auto-updates. One of our posters, Remo, posted in this thread that he was only able to get the Framework to work by this method. Here is a link that he provided to turn of updates:

      We understand this is not close to the ideal solution. If we are able to reproduce and solve this issue, we will post an update to this post. If any other reader has any suggestions on how to reproduce or even solve this issue then please post… Thank you.

      • Following the tree steps suggested from dymodev me solved, also:
        1) enabling chrome://flags/#enable-npapi
        2) closing chrome
        3) re-installing DLS

  27. Using Opera in windows XP. 1 year worked fine and now stopped working anymore with same error : “No DYMO printers are installed. Install DYMO printers.”

    On the same machine tried Google Chrome, Internet Explorer, Firefox, Midori, Canary same problem. We have never upgraded the systems. Why it stop working?

    • For both Opera and Chrome, these are probably due to the phasing out of NPAPI, please look at the base post for steps to get these to work. As to the others, more information would be needed. Make sure that you are using the latest version of the DYMO Label Framework JavaScript library and the latest DLS software.

  28. The only possible way looks like using Native Messaging:

    Looks simple, but I can imagine it’s not easy to get this done that simple.

    I don’t know how the non NPAPI plugins in chrome://plugins are designed.

  29. I would say about 33% of our company revenue is derived from a product that uses the DYMO javascript label framework for printing labels. We’ve sold so many DYMO label printers to clients we don’t even count anymore. I know the DYMO developers are working hard to find a solution to NPAPI changes in Chrome. Please keep us updated and let us know if we can help. This change is a critical — company on the line — type of thing for us. Google doesn’t seem to be living up to is “do no harm” mantra.

    • Hi Mark, We will keep you updated on any significant development. We are striving to have an alternative solution before September.
      Thanks for your patience.

  30. On the chance that anyone has the same situation as me, I tried everything suggested above with no joy.

    Until I did a complete shut down and restart of the whole computer! All working again now…

    Classic IT solution.

    • Thanks for following up with this Martha! I’m sure this will help other people that were in your situation..,

  31. we have tried all of the above!

    our systems has been working fine for months and yesterday the app in not connecting to the dymo printer generating upc codes or letting me get into it to access changes of labels etc… called dymo it is not them i can print a price on the ticket from them they assure me it is your system i have down loaded everything and followed your the steps give above help!!

  32. I have followed your directions and the DYMO label printer is still not working. Please advise.

  33. Have you tried steps below?
    Update (4/15/2015)
    With version 42 of Chrome, Google now disables NPAPI which is required to run our plugin. However, you can manually enable it by typing the following into the Chrome address bar and adjusting the setting:

    Update (4/20/2015)
    It has been our experience that just enabling NPAPI may not be enough. In some instances, close the chrome browser then uninstall and re-install the DLS software for the plugin to appear in the plugin list: chrome://plugins/
    Go here to see if your browser has the framework installed correctly: Check Environement

  34. Thank you very much for this post. We also use the DYMO Label Framework in our internal web application (that basically runs our business), though just some of us used Chrome, so it was strange to learn of the label printing not working from some people for no reason. This clears it up for us and we’ll try our options. I look forward to any solution that comes out from DYMO.

    “I think most of us are here because no one else is doing what you are with web-based label printing and we love it.”
    I completely agree.

    • Thank you, Mike. We will keep everyone updated on the progress of a solution via this website, we hope to have more information soon.

  35. This is unacceptable. You’ve just rendered my Dymo Barcode printer useless. I use it for my store to barcode inventory. When will this be fixed?

    • Hi Todd, Hopefully, you can use the steps in this post to get your application running again in Chrome. If not, it is possible to use Firefox or IE as an alternative, though we know this may not be desirable. We are actively working on a solution and will keep everyone informed about the progress.

  36. My advice to everyone here with a business that depends on the DYMO NPAPI plugin – rewrite your app to support Google Cloud Print. We’re doing this – It’s not that hard and it opens up support to every label printer, and it supports Chromebooks, Linux, iOS, and Android and every browser. You have 7 months…

  37. As alternative, you may go by much harder, but in long-term reliable way, chrome app/extension with built-in usb driver for dymo printer:
    As an on-page solution: render image (canvas) and use system printer driver through standard printing menu.

  38. This issue has just become more urgent. Since version 43 of Chrome it now displays a message on every startup saying “This site uses a plugin that will soon be unsupported”. This is very annoying and unprofessional to our customers. Found no way so far to disable this warning.

    DYMO, any news on the permanent solution?

  39. Watching this with great interest. We only need to print from an internal Chrome packaged app that we wrote for inventory management and label printing. We also use a ZPL compatible printer and send the ZPL directly to the USB endpoint of the printer using the chrome USB APIs with great effect.

    I was not able to find a native protocol for submitting XML labels to the Dymo, I’m guessing the driver does all the rendering

    We may eventually switch to hosting the printer connectivity from a service on the machine that has the printers connected exposing them via a webservice interface to allow access via a mobile app (similar to the Dymo WebSDK. In fact I’d probably just use the WebSDK for the Dymo connectivity).

    Thanks for the updates on this, and especially for detailed info on what you guys have tried and how it did, and didn’t, work out.

    • The DYMO printers don’t support ZPL. The printer driver is doing the rasterization.

      The DYMO SDK or the Windows print APIs can be used to print to the DYMO printers.

  40. Though I have enabled NAPI under chrome://flags, the “check environment”( sample fails with the new Chrome 43 64 bit on Windows 8.1. I’ve rebooted my PC to double check but still not working.

    • The “check environment” is working fine with new Chrome 43 on Windows 7 (64bit). What kind of error message gets displayed? Are the other DYMO samples working?

      • Hi pi,

        Here are the results from the check environment in chrome, no other errors reported in sample or console log. IE & Firefox have no problems.

        isBrowserSupported: true
        isFrameworkInstalled: false
        errorDetails: DYMO Label Framework Plugin is not installed

  41. google stop support NPAPI
    may on a new Customers think to install firefox so him not Up in the morning with a new “chrome” bug.

    • We are currently working on the solution. The removal of NPAPI from Chrome has a very large impact on our SDK so we are putting a significant amount of research into this in order to come up with the best solution for our customers. Our goal is to have the solution in place before NPAPI gets turned off completely in Chrome.

      When we get to a certain point in our development, we will release more information on this blog.

  42. We’ve been working on a Windows solutions using a tray application. It runs as an web service application. If you start a POST request containing the printer name, the xml, and the amount of copies. It will try and print the XML trough the given printer.

    If anyone is interested in an test version you can contact me.

    • We’ve been working on a similar (identical?) solution using node.js, just about ready to release an alpha. Perhaps we could/should collaborate. Getting CORS requests working properly is the only difficulty we’re currently having. At present we’re scripting a submit() to a form with a _BLANK target that prints the label & responds with a JS window.close() to eliminate the new tab/popup.

    • Hi Geert,

      I would be very interested in working with you on the tray application for dymo printing

    • Geert,

      Can you please send me the test version of your tray app and the instructions? My email is [email protected]


  43. Like to share the fact that your solution works perfectly!

    Im am now able to print labels again using the tray application and a slightly modified dymo javascript library.

  44. Workable solution:
    Very much in alpha or even pre-alpha, but this solves the problem for us. Open to adding new people to the sourceforge project if you’re interested in/willing to add to the project. Please use the discussion pages on sourceforge for any questions/comments related to the project.

  45. Is there no support for Chrome under Ubuntu? I cannot get it to run there.
    The check gives me: false, false, the operating system is not supported.

    Now most applications go into the clowd or are web bases (e-commerce websites!!!!) there is no need to keep throwing money to Microsoft. A lightweight PC/laptop with Linux and a browser is much cheaper.I really would like to see the work.

    • Egbert,

      Since DYMO SDK require DLS to be installed on the client machines, there is no support for SDK applications running in Chrome on Ubuntu. We do not have a Linux version of DLS.

  46. DYMO Support,
    After September, as a backup to Chrome, will Internet Explorer continue working fine with DYMO ?

  47. Thanks drobdymo.
    Our users are getting anxious seeing the warning message, when do you expect the Chrome fix to be in place?
    Also, is there a way to get rid of the warning message ?

    • We are actively pursuing a solution that can be used in Chrome and will replace the functionality that we get from NPAPI. It is not a simple issue to fix due to Google not providing a sufficient alternative to NPAPI. We have researched many different alternative methods and have narrowed down the solution. We are currently developing the new solution and we will update this blog when we have more information.

      We haven’t found any way getting rid of the warning message yet.

  48. Will the final solution Dymo will come up with be a solution that will not require any changes for the current program-code people are using? If not; Does Dymo expect that at the release of Chrome 45 the developers of multiple Dymo (code) products can change hundreds of stand-alone (local) machines (with or without testing, change of procedures, support documentation updates, config changes)?!

    This will take months… You MUST state a date of solution or fix. Please do not wait for Chrome 45 but do it before that so solution providers have a chance to fix this for our customers. It’s fair if Dymo states this is simply not possible… but then we have a choice to drop Dymo directly and search for an alternative product for all the applications in the field that requires (label) printing during the primary work processes. The daily continuity of those company’s are in stake when the Framework is not working without any short term solution.

    Thank you and please try to let higher management “know” that this problem needs to be fixed… not by Chrome 45… but before that so stuff can be fixed on all levels. If this is not possible, that Dymo chooses not to be a safe choice for enterprise label printing.

    • We are actively pursuing a solution that can be used in Chrome and will replace the functionality that we get from NPAPI. It is not a simple issue to fix due to Google not providing a sufficient alternative to NPAPI. We have researched many different alternative methods and have narrowed down the solution. The new module should integrate seamlessly which means that your current application will require no or just very minor changes in order to run with the new solution. But a new DLS version will be required since the new binaries will be part of DLS.
      Currently we are developing the new solution with an aim to be in beta in 2nd half of August. We will update our blog when we have more information.

  49. We’ve discovered a way of printing through chrome via http OR https without requiring a plugin by piggybacking on the SSL certificate used by Topaz signature pads universal driver. Simply posting your label XML to the host can get it printing. E.g.
    $.post(“”, { thing: yourLabelXml });

    Ultimately it shouldn’t be hard to make our own X509 CA root & sign a certificate. The only issue is the install tools, some of which are free software & some of which are proprietary tools made by Topaz. As a result I can’t just repackage their software & stick it on sourceforge, but it shouldn’t be too difficult to recode the pieces we need.

    I haven’t yet added the changes to the sourceforge package, but if you’re interested (possibly in helping out) you can contact me at via email: austin at apextox com
    I’ll try to have the updates on sourceforge tomorrow.

  50. Hello, do you have any news on migrating from the NPAPI plugin? I assume everyone will need to know within the coming weeks so we can plan changes to our label provider if Dymo is unable to continue offering their services.

  51. I insist on the fact that the deadline is near, and we haven’t heard from dymo for any solution post npapi.
    Guess we will have to change all printers to a different brand that will provide us with a viable solution.

  52. With Chrome 44’s release yesterday (Jul 23rd), we’re a month away from Dymo not working on Chrome. It would be great if you could post a thread new thread on the subject with timeline for beta-access, we need time to ensure development changes work & our clients get reasonable time to implement updates.

    Thank you,


  53. Hi there.

    Could you please let us know what is the latest news on label printing from Chrome?
    I have lot of clients using it and there is no time left for me to properly test and implement the new solution.

    please post the exact date when you will have the solution ready.
    or let us know if you think you will not be able to solve this then we will know that we need to find a different solution.

    waiting for your reply as soon as possible please.

  54. I have for months found it hard to believe you can not use a Dymo with chrome book or chrome box( as I have) , we have slowly been switching back to windows and finding that windows 10 is not that bad even on a tablet, will not be long before Microsoft overtake anything Android – well for office use, we dont need all the toys and apps etc.

  55. Dear DYMO support team
    could one of you please reply if the Chrome / NPAPI solution you are working on will be posted on this page or we need to follow another page?

    • Hi Art, Please reference this post for information on the Chrome/NPAPI solution:

      • Do you have any information about what you’re working on and the timing. My concern is that if we don’t have a solution on day 1 when Chrome 45 comes out my company will be in bad shape. Without knowing what you’re coming out with and when I will need to go elsewhere.

        • Hi Kevin, please check out this blog entry, , more information will be provided soon.

          • Hi dymodev,

            I’m in the same situation as a few other posters on this thread. Our business sells your Dymo printer to be used with our software that we develop mainly for School Districts.

            Some of these schools districts are “Google Schools” and use everything google for their email, browsers, storage, etc…

            They do not have the option to use other browser nor do they want to change. I would love to keep up to date on your guys solution to this problem.

            Do you have a link to that blog entry you refer to?

            Thanks in advance!

          • Hi David, Here is the current post with information on our solution:

          • Hello DYMO, do you have a date for the solution ? We need enough time to test.

          • We are currently doing a suite of tests in the anticipation of having an open Beta this week, if all goes well. Stay tuned to the blog for more details.

          • adding my concerns. if you need beta testers, count us in.

  56. Adding my concerns about DYMO and CHROME. if you need testers, count me in .

  57. WIndows 10 and Chrome and Dymo …. not a good combo for me.
    anyone else? i cant get DYMO Framework plugin to install … have uninstalled DYMO and reinstalled and rebooted several times.

    Hopefully this will be address in the beta.

    running all updates for Win10 and Chrome.

    • Hi Ej,

      This is due to the NPAPI deprecation. We’ve been doing tests on Windows 10 with the new service and have successfully used the Framework with Firefox, Chrome, IE and Edge.

  58. This is a greate solution for my new shop

  59. Hi dymodev

    You have mentioned that this week we would have some Beta solution posed here.
    This is not to push but please understand our concern too.
    We have used Dymo with several customers and all depend on the service.
    Now only one week left to end of the month I cannot see how we are going to get sufficient time to make sure we can do our tests and how we are going to get the time to go to customers and implement the solution.

    I would suggest to post whatever you have now, I am sure we can join in, have valuable input and speed up the job.


  60. “With the Chrome 45 update, the Chrome team has removed all support for external browser plugins. Previously, you were required to enable the NPAPI, but that is no longer available.”

    DYMO and Chrome no more? Do we *have* to use IE now?

  61. First of all, compliments for not being able to have a solution ready in a year time for Chrome. That’s the amount of time you had to find such a fix…. but maybe it is your manager that doesn’t understand that one of your fundamental good thing was the ability to print from Chrome. I am seriously considering to move to your competitors if you will not fix the Chrome https problem. And if you don’t make it work again on Mac very soon…

    I was using Windows 7 and despite all the annoying bugs like the security flag using https (if you don’t know it most website run in https – so making it work without any security alert is not optional) I was able to make it work again.

    I updated the operative system to Windows 10, re-installed the printer, re-installed the web service, and I have a beautiful error now: Failed to execute web service command: 400 Bad Request

    I have installed all the thing suggested in the Open Beta Announcement – please help me to fix this because I am really fed up.


    • We are working hard on this issue, We will provide you fix soon, thank you for your patience.

      • Just a quick line to apologize for the previous comment, I was having an hard time from our customers.

        And to let you know that I have fixed the problems with your latest beta2 release.

        Thanks for this, now my customers are happy again, hence so do I!!!

        Keep up the good work and roll out the fix for Mac too, I am looking forward to it!

        • Hi Marco, Thanks for your feedback and apology. We do understand that people are using our SDK for business and that can cause frustration when things don’t work. I know we were pretty frustrated to learn that Google was removing support for NPAPI and not replacing it with something that provides similar functionality but in the end I think we have something that will be better for users in the long run. So apology accepted and I’m glad things are working well for you!

        • Hi,

          Could you explain what you did to solve the problem?
          I am experiencing the same error on my machine: Failed to execute web service command: 400 Bad Request

          Installed the latest software v.

          Tried my own code and some samples from these threads, but all result in this error..


  62. Reg dymodev comment… We are working hard on this issue, We will provide you fix soon, thank you for your patience.

    So until you fix the problem I can not print my bar codes for work??? Very unprofessional. I have done every thing suggested to do to make this work, and still nothing. How soon is soon????

  63. So, just to be clear, Chrome has made things difficult for everyone. This is not Dymo’s fault, this is the browsers pulling tricks to be more “secure” when all they do is create problems.

    The Dymo label printer did work in Firefox, so you can avoid using IE if you want.
    There is a Beta – that might work with Chrome, but I have yet to test it myself.

  64. Hello, I have gone through all these steps several times to no change. In fact, it’s gotten worse and the Dymo printer, which had shown up in the system and chrome before, but simply would not work, has now disappeared from the application!
    None of your suggestions have made any difference with using this in Chrome. Please fix and advise!

  65. Hello,

    Do you have any “DYMO Web Service Beta Installer” for MacOS? Is this “solution” only for Windows?

    I just bought the DYMO LabelWriter 450 and I can only work with Firefox. Chrome doesn’t work because of NPAPI plug-ins deprecation.

    Now, couldn’t you use chrome.usb? See:

    Please, treat your SDK as your printers. There is no point on having good printers with an outdated SDK.

    • Hi, we are hard at work on the web service for MacOS. Stay tuned. We hope to release a beta in the near future.

  66. How is the progress for this issue coming along? We have users on PC and Mac who would love to be able to use Dymo with Chrome again.

  67. Starting Chrome 45 NPAPI does not exist any more and the only way to print is using the extension.

    Hope you guys can solve this issue


  68. I am trying to use a Dymo LabelWriter 450 Turbo, Mac OS X and Google Chrome browser. It’s 2016 and very hard to believe Dymo hasn’t resolved support for Mac OS. Is Dymo still stuck in the 80s?

  69. Is dymo.label.framework.checkEnvironment() still supported in the new Framework (2.0.2)?

    I’m trying to use it, but get this:

    Uncaught TypeError: P.c is not a function

    I’m looking for a means of displaying diagnostic information for available printers.

  70. Hi, I have installed DLS 8.5.3. The Label writing javascript framework(DYMO Label Framework 2.0.2) is not working in Chrome (latest). where as it is working fine in FireFox. I have installed web services also. Thought the localhost is working it showing an error “https://localhost:41951/DYMO/DLS/Printing/PrintLabel”.

    Could you help on this?

  71. You guys just really need to make a chrome plugin. There’s a very good reason Google Chrome has removed NPAPI. It’s a security risk.

  72. December 2014 was a long time ago. What’s going on? Have you got a solution yet?

  73. We are having problems with windows 8 printing the Dymo 450 Twin Turbo. It works for a couple weeks then stops. This last time we could not get it up and running. I ran the check on it and this is the message I get.
    isBrowserSupported: true
    isFrameworkInstalled: false
    isWebServicePresent: false
    errorDetails: DYMO Label Framework Plugin is not installed

    Any Help would be greatly appreciated.

  74. Am I able to use Dymo 450 on a Chromebox

  75. Is there any way to get the Dymo LabelWriter 450 to work with a Chromebook? I’ve attempted some of the solutions suggested, but all the downloads won’t open. Anything that will allow it to work? Thanks for your help.

    • Hi Aaron,

      We do not have an SDK that targets the Chrome OS. I am unaware of any tricks to make it work, either.


  76. After many trials I found out that 8.7.2 stopped working om a PC with Chrome 67 while 8.7.1 still workes on that gear. I had to revert the upgrade. What now? W10 pro, Chrome 67.xxxx, WordPress website. It might be needed to do the installation with admin rights and on a clean system (do an uninstrall before and reboot between steps).
    Egbert Jan , NL

 Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>