Click to upload or drag and drop
PDF, DOCX, PPTX, TXT, JPG, JPEG, PNG, HEIC, ODP, ODT, BMP, or TIFF
up to 20MB
Uploading...
Blackboard will not accept a Word document as a test upload. Its bulk question upload reads one thing: a tab-delimited TXT file. The workable path from Word to Blackboard is to get your questions into a spreadsheet, arrange them into Blackboard's column order, save as Text (Tab delimited), and upload that .txt file. Anthology's own help confirms the upload file "can be edited in Microsoft Excel or in a text editor," which is what makes the spreadsheet route practical rather than a hack.
This guide covers the exact row format, the rules that quietly break imports, and how to get from a chapter or manual to a finished question set in the first place. If you need the questions written as well as formatted, the Blackboard test generator handles the drafting step from your own source document.
Each file must be a tab-delimited TXT file. Not CSV. Not .xlsx. Not .docx. The separator between fields is a literal TAB character, and the structure is:
The type codes documented for the Ultra Course View are MC (multiple choice), MA (multiple answer), TF (true or false), ESS (essay), MAT (matching), FIB (fill in the blank), FIB_PLUS, and NUM (numeric). The Original Course View documents a longer list that also includes ordering, file response, and jumbled sentence types.
Row structures follow a consistent logic. A multiple-choice row is the code, then the question text, then each answer paired with the word correct or incorrect:
MC [tab] What year did the war end? [tab] 1918 [tab] correct [tab] 1916 [tab] incorrect
A true or false row is simpler: the code, the question, then true or false. An essay row is the code, the question, and optionally a sample answer. A matching row pairs each answer with its match. A numeric row takes the question, the answer, and optionally a tolerance.
Most failed Blackboard uploads are formatting problems, not question problems. These are the ones that catch people.
Answer keywords must be in English. The words correct, incorrect, true, and false are parsed literally. If your institution runs Blackboard in another language, these fields still have to be English or the row fails.
Blank lines are not ignored. Anthology is explicit: a blank line "will be processed and return an error." If you build the file in Excel and leave a spacer row for readability, that spacer will fail the import. Delete it.
Images cannot ride along. The text upload does not support images. Diagram-based questions have to be added in Blackboard afterward, or brought in through QTI instead.
Uploaded questions default to zero points. If you have not set a default point value first, every imported question arrives worth nothing. The test will look complete and score everyone at zero. Check point values immediately after any upload.
One piece of good news: a bad row fails on its own. Questions containing an error will not upload, but the valid rows in the same file still go through. You are not starting over because of one typo. Blackboard also does not check for duplicates, so if you upload the same file twice you get two copies of everything.
Anthology recommends that each batch file not exceed 250 records in the Ultra Course View. The Original Course View documentation gives 500. Both are worded as recommendations rather than hard ceilings. If you are loading a large pool, splitting it into batches of a couple hundred is the safer habit, mostly because a smaller file is much easier to debug when something fails.
Say you have a chapter, a training manual, or an existing Word test, and you want a Blackboard question pool out of it.
Draft the questions. If the questions do not exist yet, generate them from the source document rather than writing forty items by hand. Feed in the specific chapter or module rather than an entire book, so the questions stay on the material you assigned.
Review them. Cut anything ambiguous or trivially guessable before you spend effort formatting it. Formatting a bad question is wasted work.
Lay them out in Excel. One question per row. Column A is the type code, column B is the question text, and the answer columns follow the structure for that type. Keeping each question type in its own block makes the layout much easier to get right, since MC and TF rows have different shapes.
Save as Text (Tab delimited). In Excel, use Save As and pick that format explicitly. Do not save as CSV. Open the resulting .txt in a text editor and confirm the fields are separated by tabs and there are no blank lines at the end of the file, which is a common invisible failure.
Upload. In Ultra, open the test, select the plus sign, choose Upload questions from file, browse, and submit. In the Original view, go to Control Panel, then Course Tools, then Tests, Surveys, and Pools, then Upload Questions.
The text upload is not your only option. Blackboard also imports QTI 2.1 packages, through a different menu. In Ultra you go to Manage banks in the Details and Actions panel, select the plus icon, and choose Import from QTI 2.1 package. In the Original view it sits under Course Tools, then Tests, Surveys, and Pools, then Import QTI 2.1 Package.
QTI is worth using when you need images attached to questions, or when you are moving content from another system that already produces QTI. Be aware of the supported types: Ultra handles True/False, Multiple Choice, Fill in the Blank, and Essay through QTI, and True/False questions come back in as Multiple Choice because the QTI standard has no True/False type. That is expected behavior, not a bug in your file.
Also note the ZIP import for tests, surveys, and pools is Blackboard-only. It accepts packages exported from Blackboard, not a generic QTI or Moodle zip. Those go through the QTI menu instead.
If your campus is still on the Original Course View, there is a date on the calendar worth planning around. Anthology has stated that the Original Course View will be sunset on December 31, 2026, and that all institutions must move to the Ultra Course View at that time.
That matters for assessment work specifically. If you are rebuilding courses in Ultra anyway, it is a better moment to regenerate question banks from your source documents than to hand-migrate tests you wrote years ago. Regenerating from the chapter gives you fresh items aligned to the current edition. Migrating gives you the same tired questions in a new interface, plus whatever breaks in transit. Teams running training programs rather than academic courses sometimes use the same deadline to reassess whether an academic LMS is the right home at all, since employee onboarding and certification tracking have fairly different requirements from a semester course.
Can I upload a CSV of questions to Blackboard? No. CSV is not a supported question upload format. The upload reads tab-delimited TXT only. You can build the file in Excel, but you must save it as Text (Tab delimited).
Can I upload a Word document directly? No. Blackboard's question upload does not read .docx. Move the questions into a spreadsheet, format them into rows, and save as tab-delimited text.
Why did my whole file fail? Check for blank lines between records, a header row, non-English answer keywords, or fields separated by something other than a real tab character. Those four cause most failures.
Why are all my imported questions worth zero points? Uploaded questions default to zero points when no default is set. Set the default point value before uploading, or update the scores after.
Pick the chapter or manual your next test needs to cover and generate a question set from it with the Blackboard test generator, then format the rows in Excel. To build a large reusable pool instead of a single test, start with the question bank generator, or work straight from a Word file with the DOCX to quiz tool.
From the same family of tools