Note that the Table Tools will only display when the insertion point is inside an actual table. These tools look a bit different in different versions of Word, but they are contextual, that is, they show up only after you have clicked inside a table.
'Table Tools' context tab not showing for TOC in Word 2016 - I want to convert the Table of Contents to Text but can't get to the command
I have created a Table of Contents in Word 2016.
I wish to convert the table to text, however, when I select the contents of the Table, the 'Table Tools" context tab does not appear.
- I am able to update the table as needed.
- I checked in Word Options, and all the tabs are selected when I look at Customizing the Ribbon.
Thank you for helping me resolve this issue.
Microsoft 365 and Office | Word | For home | Windows
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
3 answers
Sort by: Most helpful
-
-
Charles Kenyon 160.1K Reputation points Volunteer Moderator2022-03-22T12:21:05+00:00 A Table of Contents in Word is not a Word Table but rather a *Field*.
English can be a confusing language and Microsoft has done nothing to improve that situation!
Since you are not in a Word Table, but rather in a TOC field, the contextual tab does not appear.
Even if it did, the command to convert to text would not work because it is not a Word Table.
Instead, you want to lock or unlink the TOC field.
Locking it means it will not change or update but remains a field. If you want to update it, you can unlock it and update it. Unlinking it changes it to text which can never be updated automatically.
Lock the field - Ctrl+F11
Unlink the field - Ctrl+Shift+F9
See Function Keys and Keyboard Shortcuts that Manipulate Fields and Dealing with Fields in Microsoft Word.
-
Stefan Blom 325K Reputation points MVP Volunteer Moderator2022-03-22T12:21:41+00:00 To convert your TOC to text, you will have to unlink the TOC field. See Charles's reply.