{"id":2211,"date":"2026-07-28T07:04:21","date_gmt":"2026-07-27T23:04:21","guid":{"rendered":"https:\/\/xlwings.net\/blog\/?p=2211"},"modified":"2026-03-28T10:47:01","modified_gmt":"2026-03-28T10:47:01","slug":"how-to-use-applicationusedobjects-in-the-xlwings-api-way","status":"publish","type":"post","link":"https:\/\/xlwings.net\/blog\/how-to-use-applicationusedobjects-in-the-xlwings-api-way\/","title":{"rendered":"How to use Application.UsedObjects in the xlwings API way"},"content":{"rendered":"\n

The Application.UsedObjects<\/code> property in Excel’s object model provides a powerful way to access all objects that are currently in use within a workbook. In the context of xlwings, this property is exposed through the api<\/code> property, allowing Python scripts to programmatically inspect and manage the resources consumed by an Excel instance. This is particularly useful for debugging memory issues, monitoring application performance, or programmatically cleaning up objects to prevent memory leaks in long-running automation tasks.<\/p>\n\n\n\n

Functionality<\/strong>
The primary function of Application.UsedObjects<\/code> is to return a Workbooks<\/code> collection that represents all objects\u2014such as ranges, charts, shapes, and named ranges\u2014that are currently allocated in memory. This collection includes objects from all open workbooks. By accessing this property, developers can get a count of used objects or iterate through them to perform specific actions, like checking their properties or releasing them if necessary.<\/p>\n\n\n\n

Syntax in xlwings<\/strong>
The xlwings library provides a Pythonic interface to Excel’s COM API. To access the UsedObjects<\/code> property, you must first obtain the Excel Application<\/code> object via xlwings. The typical syntax is:<\/p>\n\n\n\n

import xlwings as xw\n\n# Connect to the active Excel instance or start a new one\napp = xw.apps.active.api # or xw.App().api for a new instance\n\n# Access the UsedObjects property\nused_objects = app.UsedObjects<\/code><\/pre>\n\n\n\n
Here, app<\/code> is an xlwings proxy to the Excel Application<\/code> object, and .api<\/code> is used to access the underlying COM object. The UsedObjects<\/code> property returns a collection that can be treated similarly to other Excel collections in xlwings.<\/p>\n\n\n\n
Parameters and Usage<\/strong>
The UsedObjects<\/code> property does not accept any parameters. It is a read-only property that provides a Workbooks<\/code> collection. Key points to note:<\/p>\n\n\n\n
    \n
  • The collection’s Count<\/code> property gives the total number of used objects.<\/li>\n\n\n\n
  • You can iterate through the collection using a for<\/code> loop or access individual items by index (1-based indexing, as is standard in Excel VBA).<\/li>\n\n\n\n
  • Each item in the collection is an object that can be of various types (e.g., Range<\/code>, Chart<\/code>, Shape<\/code>). You may need to inspect the object’s type to perform type-specific operations.<\/li>\n<\/ul>\n\n\n\n
    Example Code<\/strong>
    Below is an xlwings API code example that demonstrates how to use the Application.UsedObjects<\/code> property to list all used objects and their types in the active Excel instance:<\/p>\n\n\n\n
    import xlwings as xw\n\n# Connect to the active Excel application\napp = xw.apps.active.api\n\n# Get the UsedObjects collection\nused_objects = app.UsedObjects\n\n# Print the count of used objects\nprint(f\"Total used objects: {used_objects.Count}\")\n\n# Iterate through each used object and display its type and address (if applicable)\nfor i in range(1, used_objects.Count + 1):\n    obj = used_objects.Item(i)\ntry:\n    # Try to get the address for Range objects\n    if hasattr(obj, 'Address'):\n        print(f\"Object {i}: Type={obj.__class__.__name__}, Address={obj.Address}\")\n    else:\n        print(f\"Object {i}: Type={obj.__class__.__name__}\")\nexcept Exception as e:\n    print(f\"Object {i}: Error accessing properties - {e}\")\n\n# Example: Release objects (if needed, by setting to None or closing workbooks)\n# Note: Directly releasing objects from UsedObjects may require careful handling to avoid crashes.<\/code><\/pre>\n\n\n\n
    <\/p>\n","protected":false},"excerpt":{"rendered":"
    The `Application.UsedObjects` property in Excel's object model provides a powerful way to access all…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[25],"tags":[],"class_list":["post-2211","post","type-post","status-publish","format-standard","hentry","category-xlwings-api-reference"],"_links":{"self":[{"href":"https:\/\/xlwings.net\/blog\/wp-json\/wp\/v2\/posts\/2211","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/xlwings.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/xlwings.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/xlwings.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/xlwings.net\/blog\/wp-json\/wp\/v2\/comments?post=2211"}],"version-history":[{"count":2,"href":"https:\/\/xlwings.net\/blog\/wp-json\/wp\/v2\/posts\/2211\/revisions"}],"predecessor-version":[{"id":3381,"href":"https:\/\/xlwings.net\/blog\/wp-json\/wp\/v2\/posts\/2211\/revisions\/3381"}],"wp:attachment":[{"href":"https:\/\/xlwings.net\/blog\/wp-json\/wp\/v2\/media?parent=2211"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/xlwings.net\/blog\/wp-json\/wp\/v2\/categories?post=2211"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/xlwings.net\/blog\/wp-json\/wp\/v2\/tags?post=2211"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}