ABOUT PACKWINK
Work on the source locally, then keep the result as a file.
MD.SAVE turns web documents into .md, TAB.REC records class or meeting audio playing in Chrome, and PDF.ABLE reads, merges, and splits PDFs. The main work begins without sending the source to a separate processing server. The PackWink hub explains the difference between the three tools and publishes steps checked in the public releases.
Start on the first screen
MD.SAVE opens on the editor, where you can paste or open a file. After installing the TAB.REC Chrome extension, you can record from the tab you are using. PDF.ABLE shows a preview after you choose PDFs or images on the web.
Local work does not require an account. Sign-in is used only when you choose to keep a copy in MD.SAVE Cloud Beta.
Separate local work from a Cloud copy
MD.SAVE local editing and conversion, TAB.REC recording, and PDF.ABLE PDF work run in the browser or on the device. MD.SAVE sends Markdown to Cloud Beta only after a signed-in user selects ‘Save a copy to Cloud.’ It does not save or sync automatically.
MD.SAVE for documents, TAB.REC for online recordings, PDF.ABLE for PDFs
Open a web document or Markdown file in MD.SAVE. Record the audio playing in a Chrome tab with TAB.REC, or clean an existing recording in TAB.REC Studio. Use PDF.ABLE to read, merge, split, or convert a PDF. Your task selection on the home page stays on that screen.
You can also export saved times and notes from TAB.REC as Markdown and arrange them into meeting notes in MD.SAVE. Neither tool provides automatic transcription or automatic summarization.
Built and checked by the operator
The PackWink operator directly manages product planning, development, deployment, and guide verification. Each guide is rerun in the public release and names a reproduction sample and an unsupported or limited case.
When a release changes the screen or behavior, we revise the passage, public sample, and check date. You can report an error without sending the source document or recording.