calibre Custom Column Not Showing: How to Fix It

You created a custom column in calibre, but it is missing from the book list, unavailable in Edit metadata, impossible to edit, or producing no search results. In most cases, the column was created successfully but calibre needs to restart, the column is hidden, the wrong library is open, the lookup name is being confused with the display name, or the selected column type is calculated rather than editable. The steps below isolate each possibility without risking your books or library database.

1. Confirm the Symptom With a Small Safe Test

Before changing plugins, reinstalling calibre, or moving your library, determine whether the problem affects the column definition, its visibility, its values, or only a particular view.

1.1 Verify that the column exists

Open Preferences > Add your own columns. Find the column in the list and check these three details:

• Lookup name: The internal field name, normally beginning with a #, such as #readingstatus.
• Column heading: The human-readable display name, such as Reading Status.
• Column type: The kind of information the field stores or calculates.

If the column appears here, its definition exists in the current library. Do not create another column with a similar name. Continue by checking the view and edit controls.

If it does not appear, first confirm that you are viewing the same calibre library in which you created it. Custom columns belong to an individual library. Switching libraries can therefore make a column appear to have vanished even though it remains available in the original library.

1.2 Create a simple test column

If you are unsure whether custom columns work at all, create a temporary test column:

1. Open Preferences > Add your own columns.
2. Choose the option to add a custom column.
3. Use teststatus as the lookup name.
4. Use Test Status as the column heading.
5. Select a basic text column type intended to store one value.
6. Apply the change and restart calibre if prompted.

After calibre reopens, return to the book list and look for Test Status. Select one book, press E to open Edit metadata, and enter a short value such as Checked.

Success means the heading appears, the value can be saved, and reopening Edit metadata shows the same value. If this test works, calibre's custom-column system is functioning. Stop making broad application or operating system changes and focus on the configuration of the original column.

2. Check the Custom Column Definition and Display Settings

A calibre custom column can exist in the library database without being visible in the current book-list layout. It can also be visible but not directly editable because of its type.

2.1 Restart calibre when the interface requests it

Creating or changing a custom column can require calibre to restart before every part of the interface recognizes the new database field. Close and reopen calibre normally, or accept the restart prompt shown after applying the change.

Do not merely close the Preferences window and assume the new field should appear immediately. If calibre is minimized to the system tray, make sure the application actually exits rather than leaving the existing process running.

After the restart, reopen the correct library and check both the book list and Edit metadata. If the column is now available, the change has loaded correctly and no further troubleshooting is necessary.

2.2 Unhide the column in the book list

The column may be present but hidden. In the main library view, right-click a column heading and inspect the available column choices. Enable the missing custom column if it is unchecked or marked as hidden.

You can also review the relevant book-list column configuration under Preferences. Confirm that the column is enabled for display, then return to the library view. If the column appears at the far right, drag its heading to a more convenient position.

A very wide window layout, many existing columns, or horizontal scrolling can make a newly added field easy to overlook. Scroll all the way across the book list before concluding that it is absent.

2.3 Make sure you are using the book list

Cover grid, Bookshelf, Quickview, Book details, the e-book viewer, and the metadata editor are separate interfaces. A field displayed in one is not automatically shown in all the others.

Switch to the standard book list while testing. Once the column works there, configure other views separately if you want them to display its value. For example, Cover grid can be configured to show a selected field beneath covers, while Quickview has its own choices for displayed columns.

2.4 Distinguish the lookup name from the display name

The column heading is what people see. The lookup name is what calibre uses in searches, templates, plugboards, command-line operations, and many advanced settings.

For example, a column might have:

• Display heading: Reading Status
• Lookup name: #readingstatus

Searching for Reading Status:Finished will not address that field. Use its lookup name instead, such as #readingstatus:Finished. You can confirm a custom column's lookup name by hovering over its heading in the book list.

2.5 Check the selected column type

The type controls how calibre stores, edits, sorts, and searches the information. Choose it according to the value you actually need:

• Text: Suitable for one text value, such as a location or status.
• Comma-separated text: Suitable for multiple tag-like values.
• Yes/No: Suitable for a state such as read, owned, or reviewed.
• Integer or floating-point number: Suitable for numeric data.
• Date: Suitable for dates rather than date-like text.
• Series: Suitable for a custom series with an associated index.
• Enumeration: Suitable for values selected from a predefined list.
• Long text: Suitable for notes or longer comments.
• Column built from other columns: Suitable for a value calculated from a template.

If the field appears but cannot be typed into, check whether it is a column built from other columns. This calculated field is sometimes informally described as a virtual column. Its displayed result comes from its template, so it is not edited like an ordinary text field. Edit the source metadata or the template instead.

If you intended to enter values manually, create an editable text, numeric, date, Yes/No, series, or enumeration field as appropriate. Avoid deleting the original until the replacement has been tested.

2.6 Do not confuse Virtual libraries with custom columns

A Virtual library filters the existing library to a subset of books. It is not an editable metadata column. If you created a Virtual library named Unread, it will not appear as a field in Edit metadata.

You can base a Virtual library on a custom column, but the two objects have different purposes. First create and populate an editable custom column. Then, if desired, create a Virtual library whose search uses that column.

3. Check the Library, Metadata, Search, and Connected Features

Custom columns are primarily calibre library metadata. They are not automatically embedded in every e-book file, displayed by every reader, or exposed identically through every calibre feature.

3.1 Confirm the active library

Look at calibre's library selector or window information and verify the library path. Switch to the library where the column was originally created, then reopen Preferences > Add your own columns.

If the column exists in one library but not another, calibre is working normally. Recreate the definition in the other library only if you genuinely need the same field there. Matching display names do not automatically synchronize column definitions or values between libraries.

3.2 Test editing through Edit metadata

Select one book in the main list and press E. Look through the custom metadata section for the field. Enter a value, save the dialog, and reopen it.

If the field is present in Edit metadata but hidden in the book list, the problem is the list configuration. If it is visible in the list but missing from Edit metadata, recheck whether it is a calculated column or a field type presented differently by the editor.

3.3 Use the correct custom-column search syntax

Custom-column searches use the lookup name, including the leading #. Examples include:

• #readingstatus:Finished to find matching text.
• #readingstatus:true to find books where the field has a value.
• #readingstatus:false to find books where the field is empty.
• #read:yes to find a Yes/No field set to Yes.
• #score:>=8 to search a numeric field.
• #myseries_index:>2 to search the index of a custom series field.

Search results can also be restricted by an active Virtual library. If a correct query finds nothing, switch to the full library, clear the existing search, enter a known test value in one book, and search again.

Success means the test book appears when you search its exact stored value. Stop changing column settings at that point. Any remaining issue is likely limited to a saved search, Virtual library, or view filter.

3.4 Understand metadata downloads and conversions

Downloaded metadata usually updates supported standard fields such as title, authors, identifiers, tags, comments, or publisher. It does not guarantee that a personally defined custom field will be populated.

Likewise, converting an e-book does not make a calibre custom column appear inside the text of the book or in the e-book viewer. A custom column remains library metadata unless a specific calibre template, plugboard, catalog setting, export workflow, or device integration uses it.

If the column works in the library but is absent from a converted book, that is not evidence that the custom column is broken. Check the exact conversion or export feature and whether it supports the field's lookup name.

3.5 Check device and Content server expectations

A connected reader may support only its own fixed metadata fields and collections. It may not display arbitrary calibre custom columns. Device drivers, templates, and metadata plugboards can use selected calibre metadata in supported situations, but the reader's interface determines what appears on the device.

The Content server also has its own browser interface and display behavior. First confirm that the column works in calibre's desktop library. Then restart or refresh the server view and test without a stale browser page. Do not change USB mode, firewall rules, or email settings when the column is missing only from the local book list, because those systems do not control local column creation.

4. Check Plugins, Permissions, and Library Storage Only When Relevant

Operating system and storage problems are less common than a hidden column or incorrect field type. Investigate them only if changes cannot be saved, disappear after restarting, or behave differently in a clean test library.

4.1 Test without third-party plugins

A plugin that modifies the book list, metadata editor, library view, or interface layout could interfere with how a field is presented. If the problem began after installing or updating a plugin, disable that plugin temporarily and restart calibre.

Advanced users can also launch calibre while ignoring custom plugins using the supported command-line option for that purpose. If the column appears in that session, re-enable plugins individually until the conflict returns.

Do not remove every plugin at once unless you have recorded the existing configuration. The goal is to isolate one variable, not to rebuild calibre unnecessarily.

4.2 Check whether the library is writable

If a value appears to save but disappears after restart, verify that your user account can write to the calibre library folder and its database. This is especially relevant after copying a library from another computer, restoring a backup, changing ownership on Linux or macOS, or placing the library in a protected Windows folder.

Do not edit metadata.db manually. Also avoid granting broad system-wide permissions. Give your normal user account appropriate access to the specific library folder, then test one metadata change.

4.3 Treat cloud synchronization carefully

Live synchronization tools can create conflicts if they modify or replace library files while calibre is open. Pause synchronization briefly, close any second calibre instance using the same library, and repeat the one-book test.

If the value now remains saved, the issue is likely concurrent access or synchronization rather than the column definition. Keep a proper backup and avoid allowing multiple computers to write to the same active library database simultaneously.

5. Use Debugging Tools Without Overcomplicating the Problem

Logs are useful when the interface fails to save a definition, calibre reports an error, or a plugin appears involved. They are usually unnecessary when the only problem is a hidden heading.

5.1 Restart in debug mode

Open the menu attached to Preferences and choose Restart in debug mode. Reproduce the problem once: open the custom-column preferences, attempt the edit, save a value, or switch views. Then close calibre so the debug information can be displayed or saved.

Look for messages mentioning the library database, custom fields, metadata, permissions, or a named plugin. A debug log is most useful when it records one controlled attempt rather than a long session containing unrelated actions.

5.2 Confirm the database field with calibredb

Users comfortable with a terminal can use calibre's calibredb custom_columns command to list custom fields known to the selected library database. The detailed option can provide additional information.

If the field appears in that list but not in the graphical book list, concentrate on the interface layout, active library, and plugins. If it is absent, the definition was not created in the library being queried.

Command-line tools must point to the intended library, especially when the Content server or another calibre instance is involved. Do not remove or recreate database fields from the command line merely to fix a visibility problem.

5.3 Skip unrelated logs

Device detection logs, conversion debug output, news-download jobs, and email delivery logs do not normally explain why a custom column is missing from the desktop book list. Use them only if the field works locally and the failure occurs specifically during that operation.

This distinction prevents a simple display problem from becoming an unnecessary device, network, or conversion investigation.

6. Run a Clean Temporary Test Before Reinstalling

Reinstalling calibre normally does not repair a hidden column, change a calculated field into an editable one, or add a library-specific definition to a different library. A temporary test is faster and preserves your existing setup.

1. Create a new empty folder in a local location you can write to.
2. Use calibre's library controls to create or switch to a temporary library in that folder.
3. Add one DRM-free test document or create an empty book record.
4. Create a simple text custom column.
5. Restart calibre if requested.
6. Enable the column in the book list.
7. Enter a value through Edit metadata.
8. Search for it using the lookup name.

If every step works, the calibre installation is functioning. Return to the original library and investigate its column definition, view settings, permissions, filters, or plugin interactions. Do not reinstall or delete the original library.

If the clean library also fails, restart without custom plugins and collect a concise debug log. Reinstallation should be considered only after the same failure occurs with a new local library and plugins excluded.

7. Quick Fix Checklist

• Open Preferences > Add your own columns and confirm the field exists.
• Verify that you are in the library where the column was created.
• Restart calibre after creating or changing the field.
• Right-click a book-list heading and enable the hidden column.
• Scroll horizontally to check whether it was added at the far right.
• Switch from Cover grid or Bookshelf to the standard book list.
• Use the lookup name, such as #readingstatus, in searches and templates.
• Confirm that the field type is editable rather than calculated.
• Enter a test value through Edit metadata and reopen the book.
• Clear searches and switch out of any restrictive Virtual library.
• Temporarily disable relevant interface or metadata plugins.
• Test a new local library before reinstalling or modifying the original database.

Stop troubleshooting as soon as the column is visible, editable when appropriate, retains a saved value, and returns the expected book in a lookup-name search. Changing additional settings after success can introduce a second problem.

8. Frequently Asked Questions

8.1 Why does my calibre custom column appear in Preferences but not the book list?

It is usually hidden, positioned beyond the visible right edge, or unavailable until calibre restarts. Right-click a book-list heading, enable the field, and check the full width of the list.

8.2 Why can I see the column but not edit it?

It may be a column built from other columns. That type calculates its value from a template and is not manually editable. Change the source metadata or template, or create an editable field type.

8.3 Why does searching the display name return no results?

calibre searches custom fields by lookup name. If the heading is Reading Status and the lookup name is #readingstatus, search with an expression such as #readingstatus:Finished.

8.4 Why is the column missing after I switch libraries?

Custom-column definitions are library-specific. Switch back to the original library or create an appropriate field in the other library. Confirm the lookup name and type rather than relying only on a matching heading.

8.5 Should a custom column appear on my e-reader?

Not automatically. Reader devices generally expose a fixed set of metadata fields. calibre may use custom metadata through supported templates, plugboards, catalogs, or device features, but the device decides what its interface can display.

8.6 Will reinstalling calibre restore a missing custom column?

Usually not. The field belongs to the library database, while its visibility can depend on interface configuration. Test the active library, restart, unhide the field, verify its type, and run a temporary-library test before reinstalling.