Heidegger Gesamtausgabe

Martin Heidegger's complete works.

Register to see the Bände (volumes) »

This is a simple page to introduce the GA App at this web site.

What is it?

The GA App was written as a tool for generating a web page listing the complete works of Heidegger. Since the first version, I have been adding ancillary content to have it readily available.

The Gesamtausgabe page at beyng.com is accessible to anyone looking for information. This GA app presents the Gesamtausgabe in a different way from on the single page at beyng.com. I have been adding additional features, like full-text search, to make it more useful. If you look up Heidegger's works on a regular basis, you might find this app useful too.


Currently the database has all GA titles, English translations, editors and translators, and many of their books and papers. That's similar to the information currently on beyng.com, but organized as an information application instead of a collection of pages.

If you are interested in adding your content to this GA app, send me an email.


Search currently looks inside the metadata of books (e.g., titles, authors, etc.), in glossaries, some books, and a limited number of papers. To search inside books, your best bet is to follow the links from this app, to Google Books or Amazon, and search inside the book there.

I have standardized person's names to their most common citations — e.g., "Bill Richardson" -> "William J. Richardson" — when the name is an author, translator, or editor. That makes it easier to connect documents.

Heidegger Circle

Members of the Heidegger Circle can access papers from the Heidegger Circle proceedings.

If you are a member of the Heidegger Circle, and proceedings links don't work, send me an email.

Content II

I am adding additional content regularly. The app is like a combination of Google Books and Google Scholar, but with domain specific knowledge; e.g., it'll know how to follow GA links in citations.

Some of the data is private. I have some ebooks on OneDrive, and I've linked to them, but only the authors, editors, translators and collaborators can access them. If you cannot access your book, send me an email and I'll associate your login in the database. You might need to have a Microsoft id to access OneDrive.

Because citations often include line numbers, pages from the GA are presented with lines breaks similar to the original. Other texts are formatted to follow the look of original, while allowing the text to adapt to the display area. To improve indexing for search, end-of-line hyphenated words are connected.

Search considerations

The app diacritizes some words to improve hints and searches — e.g., Holderlin -> Hölderlin; αληθεια -> ἀλήθεια. It also substitutes some words — aletheia -> ἀλήθεια. If you can use Greek polytonic keyboard or paste terms in the search box great, but, if you are typing on a mobile, try unaccented Roman characters.

I considered indexing the GA content and related papers that are available on the internet, but the quality of the texts out there is too low to make that practical. Fewer than 5% of the texts don't have OCR errors, non-standard Greek characters, missing umlauts, or syllabification (Is that Da-sein, or Dasein hyphenated at the end of a line?), and their citations aren't linked, and many files are slow to load. So instead, I've started editing texts and managing them in the app, so that they'll show up in search results. Since it is impractical to edit every text, I have started with the most cited.

As a rule, I have left titles with their original spellings, but standardized words in texts. Greeks words have been standardized to Unicode with polytonic diacritics — replacing characters invented before PCs supported Unicode and Romanizations from the days of typewriters. The search hints might suggest using "λόγος" for "logos", but you'll want to search with both to find everything.

Searches OR the search terms. Searching for "Richard Polt", will return every document containing either "Richard" or "Polt". Searches do not support Boolean operators nor quotes to mark exact phrases.

Before searching the indexes, the app first tries for an exact match. Searching for "71" or "Das Ereignis" will return GA 71.

Authentication and Authorization

The web site needs to authenticate who is using it for two reasons. It uses SSL to encrypt communications with your browser, to keep others from reading your traffic. It uses roles to manage which users are authorized to make changes and access additional content. You need to register and create a login in order to use the app.

Register »


Currently the app is not hooked up to an email system. So the app cannot yet send you an email to reset your password. If you forget your password, you'll have to re-register. You should use a valid email address for your login, in anticipation of when email is turned on. Or, if you are uncomfortable using your email address, you can just make up a name, with an @ in it.

For the app to send emails, (e.g., password reminders) I need to move it from azurewebsites.net to its own domain name.


Should the app fail catastrophically, I can rebuild it and reload the initial set of data automatically. I'm planning to have getting information changed in the app flow back into the initial data set.

Should the app's database get corrupted, I can request a database restore from Azure, or delete the database and the web site will recreate it from the initial data set.

When the database is rebuilt, the logins will be lost (password hashes are generated per database), and you'll have to re-register. If re-registering is annoying, you can email me your login and password, and I'll add them to the initial data set, so that they will get added automatically whenever the database is rebuilt.


The web site uses browser cookies to manage your session; so you don't have to keep logging in. I've configured the app to trust cookies for 30 days, but server updates may recycle cookies, requiring that you login again.

The web site currently uses a self-signed certificate for SSL. When this site moves from azurewebsites.net to its own domain name, I'll figure out how to get a registered certificate.