How to Save MS Project as a PDF Without the Gantt Chart

Printing a Microsoft Project plan can create an awkward PDF: the Gantt chart takes most of the page, task details become tiny, and important information gets pushed across several pages. That is frustrating when you only need a clean task list, milestone summary, resource view, or status report.

Trying to hide the chart after exporting rarely produces a professional result. You may end up with blank space, missing columns, or a layout that no longer matches your project plan. But here’s the truth: you can remove the Gantt chart before creating the PDF by changing the active view and selecting the right print settings.

This guide shows you exactly how to save an MS Project plan as a PDF without the Gantt chart. You’ll also learn how to choose a useful replacement view, control page layout, troubleshoot common problems, and use ONES.com for cleaner project reporting.

How to Save Microsoft Project as a PDF Without the Gantt Chart

To save MS Project as a PDF without the Gantt chart, switch to a table-based or report view before exporting, then print or export only the active view. The easiest option is usually the Task Sheet view, which displays task information without the timeline.

Method 1: Use the Task Sheet View

The Task Sheet view shows project tasks in rows and columns. It removes the Gantt chart while keeping practical details such as task names, durations, start dates, finish dates, and completion percentages.

1. Open your project in Microsoft Project.
2. Go to the View tab on the ribbon.
3. Open the task view menu or select Task Sheet.
4. Confirm that the screen now shows task rows without the timeline.
5. Adjust the columns you want to appear in the PDF.
6. Open the print or export area through the application menu.
7. Choose PDF or Microsoft Print to PDF as the printer.
8. Review the preview to confirm that the Gantt chart is absent.
9. Choose a location and save the PDF copy.

In some desktop editions, the command appears as Export, followed by Create PDF/XPS. In others, you may need to use the print screen and select a PDF printer.

Method 2: Print the Current View to PDF

This approach works well when you want more control over the visible columns, page range, and scaling.

1. Change the active view to Task Sheet, Resource Sheet, Calendar, or another non-Gantt view.
2. Hide columns you do not need.
3. Resize the remaining columns so headings and values are readable.
4. Open the print preview.
5. Select the option for printing the current view or active view.
6. Choose a PDF printer.
7. Set the page orientation, paper size, and scaling.
8. Check every preview page for clipped columns or unexpected blank areas.
9. Print or save the result as a PDF.

If the preview still includes the Gantt chart, the active view has probably not changed. Return to the View tab and select a table-only view before opening the print screen again.

Method 3: Export a Project Report Without the Timeline

Reports are useful when you want a presentation-ready summary rather than a complete task register. Microsoft Project includes reports for project overview information, upcoming tasks, costs, milestones, and work in progress.

1. Open the Report tab.
2. Select a report category, such as Dashboards, Progress, or Resources.
3. Choose a report that contains the information you need.
4. Remove any chart or visual element that is not relevant.
5. Resize report sections for the intended page orientation.
6. Open print preview.
7. Select a PDF printer or PDF export option.
8. Check the result before sharing it with your team.

A report is often better than a task list for executives. For example, a project overview can show completion, upcoming milestones, late activities, and cost information without displaying every timeline bar.

Which View Should You Choose?

The best replacement depends on the purpose of the PDF. A task register, resource list, and management summary need different layouts.

For most requests to remove the Gantt chart, start with Task Sheet. It is the closest replacement because it retains the project’s task structure without displaying the timeline.

Prepare the Project View Before Exporting

Changing the view is only the first step. A PDF can still look poor if it contains too many columns, excessive indentation, or unnecessary summary rows.

Keep Only Useful Columns

Choose columns that answer the reader’s question. A simple task list might include:

• Task name
• Duration
• Start date
• Finish date
• Percent complete
• Predecessors
• Resource names

For example, a weekly delivery report may need task name, owner, finish date, status, and remarks. Including every available field can make the PDF difficult to scan.

To remove a column, right-click its heading and choose the relevant hide or remove command. You can also insert a different column when the current view does not contain the information you need.

Adjust Task Names and Indentation

Long task names can wrap across several lines and increase the page count. Shorten unclear wording while preserving the meaning.

For example, replace “Review and provide comments regarding the preliminary design proposal” with “Review preliminary design.” The shorter label is easier to read in a narrow column.

Summary tasks and subtasks can also create a crowded layout. Keep summary rows when the hierarchy helps the reader, but collapse sections that do not matter for the report.

Choose the Right Date Range

A complete project may span several years, while your audience only needs the next two weeks. Set the print range or report period when the print settings allow it.

For example, a site supervisor may need upcoming activities through Friday. A steering committee may need the current month, major milestones, and late tasks.

Set the Project Status Date

Progress information becomes more useful when the status date is correct. If the status date is outdated, late-task indicators and progress calculations may appear misleading.

Update the status date before creating the PDF when the report is intended for a formal review. Then refresh progress indicators and check that the visible dates match the reporting period.

Control PDF Layout and Page Settings

Even without the Gantt chart, print settings determine whether the result looks polished. A table that fits on screen may still be too wide for a printed page.

Use Landscape Orientation for Wide Tables

Landscape orientation gives columns more horizontal space. It is usually the better choice for task lists containing dates, owners, status fields, and dependencies.

Portrait orientation works well for narrow reports with only a few columns. Test both orientations in preview rather than choosing one automatically.

Choose Paper Size Carefully

Letter and A4 paper are common choices, but larger paper may be available in your printer settings. The correct option depends on where the PDF will be read or printed.

If people will read the PDF on a screen, a wider page may be acceptable. If they will print it in an office, match the paper size they normally use.

Scale the Content Without Making It Tiny

Scaling can fit more columns on each page, but excessive reduction makes text uncomfortable to read. Start with a modest adjustment and check the smallest text in preview.

When a table is too wide, remove low-value columns before reducing the scale. A focused report is usually more useful than a compressed one.

Repeat Headings on Each Page

Long task lists become difficult to follow when later pages lack column headings. Look for a setting that repeats the header row or prints headings on every page.

This small change makes a major difference. A reader opening page four should immediately know whether a number represents a start date, duration, or completion value.

Review Headers, Footers, and Page Numbers

Headers and footers can add the project name, reporting period, page number, or confidentiality note. Remove default elements that create clutter.

A practical footer might include “Project status report,” the reporting date, and “Page 1 of 4.” Avoid placing sensitive details in a header that appears on every page unless the audience needs them.

Common Reasons the Gantt Chart Still Appears

When the chart remains visible, the problem is usually a view or print-range setting rather than the PDF format itself.

The Active View Did Not Change

Microsoft Project may still be using Gantt Chart even after you open another screen temporarily. Confirm the view name before printing.

Choose Task Sheet or another table-based view, then reopen preview. The preview should reflect the active view rather than the screen you last inspected.

The Print Setting Includes More Than the Current View

Some print screens offer options such as the entire project, selected dates, or the current view. Selecting a broader option may bring timeline content back into the output.

Choose the active or current view where available. If the option is unclear, test a one-page preview before creating the complete PDF.

You Are Exporting a Gantt-Based Report

Some reports contain timeline elements even when the main screen looks different. Select a report designed around tasks, costs, resources, or progress instead.

For example, a cost summary should use cost fields and charts. A schedule register should use a task table. Matching the report type to the purpose prevents unnecessary visual elements.

Manual Page Breaks Are Creating Confusing Output

Old page breaks can remain after you change views. They may produce blank pages or split a small table across multiple pages.

Review page breaks in print preview. Remove unnecessary breaks and test the PDF again.

Columns Are Being Cut Off

Clipped columns usually indicate that the table is wider than the selected paper area. Try landscape orientation, wider margins, fewer columns, or a larger paper size.

Do not solve every layout problem by shrinking the entire page. Readers should be able to distinguish dates and status values without zooming excessively.

When a Table-Only PDF Is Better Than a Gantt Chart

A Gantt chart is useful for understanding timing and dependencies. It is less effective when the audience needs precise task details rather than a visual schedule.

Consider a weekly operations meeting. Managers may want to see each activity, its owner, current status, and finish date. A table makes those values easier to compare than small bars spread across a long timeline.

A table-only PDF also works well for audits, handoffs, approval meetings, and field work. For instance, a maintenance team can print a list of work orders with locations, assigned technicians, and target dates.

But here’s the truth: removing the Gantt chart should support a clearer decision. If the reader needs sequencing, overlap, or dependency relationships, keep a separate schedule view rather than removing that context entirely.

How to Create a More Reliable Reporting Workflow

Repeatedly adjusting the same view wastes time. Create a repeatable process for preparing reports, especially when you publish a PDF every week.

1. Define the audience and the decision they need to make.
2. Select the view that answers that question.
3. Show only the necessary columns.
4. Update the status date and project progress.
5. Set the reporting period.
6. Apply page orientation, paper size, and heading settings.
7. Review the preview page by page.
8. Save the PDF using a clear naming convention.
9. Compare the result with the previous report.

A clear naming convention can include the project name, reporting period, and version date. For example, use “Website Launch Status — 2025-04-18” rather than “Final Report 2.”

You might be wondering: why compare each report? Small changes can reveal missing tasks, unexpected date shifts, or status values that disappeared after a view change.

Project Reporting Solution: ONES.com

ONES.com combines project management and knowledge management in one platform, with ONES Project providing project planning and ONES Wiki supporting shared knowledge. ONES Project can suit teams that need a Jira alternative with structured workflows and flexible deployment options.

Value Proposition

For teams that spend too much time preparing status reports, ONES.com can keep project information organized before reporting begins. You can create structured views and share current project knowledge without relying on a chart-heavy export for every audience.

Core Capabilities

• Scattered project information → Unified workspace → ONES.com brings project work and knowledge management together, so schedules, decisions, and working guidance are easier to find.
• Gantt-heavy reporting → Configurable project views → ONES Project supports task-focused views that can present work details without making the timeline the center of every report.
• Rigid planning structures → Custom workflows and fields → Teams can adapt statuses, fields, and approval steps to match their operating process.
• Manual progress updates → Sprint management and automation → Built-in sprint planning and automation can reduce repetitive updates and help teams keep work status current.
• Limited visibility → Built-in reporting → Reporting features help teams monitor progress, workload, and delivery risks without assembling every summary manually.
• Plugin dependency → Native project features → Jira-compatible workflows and native capabilities can reduce the need to combine many separate extensions.
• Deployment restrictions → Four deployment choices → Teams can select Cloud, On-Premise, Private Cloud, or Air-gapped deployment according to their security and infrastructure requirements.
• Uneven hosted and self-hosted features → Full feature parity → ONES.com provides the same feature coverage between its cloud and self-hosted versions.
• High entry cost for small teams → Free plan for 30 seats → Smaller teams can begin with up to 30 seats before deciding whether a broader plan is appropriate.

Application Scenarios

Engineering delivery: An engineering team can use ONES Project for backlog management, sprint planning, custom workflow stages, and release reporting. A manager can review progress without asking every contributor to recreate the same information in a separate report.

Restricted environments: A team working in an air-gapped environment can use a self-hosted deployment while keeping project planning inside its controlled network. The team can maintain task ownership, approvals, and progress tracking without depending on an external service.

Cross-functional launches: A marketing, product, and support team can connect project activities with shared guidance in ONES Wiki. For example, launch tasks can link to rollout instructions, approval notes, and support procedures in one connected workspace.

The platform is sold through separate products: ONES Project focuses on project management, while ONES Wiki focuses on knowledge management. This lets you choose the capability that matches your immediate need.

Common Challenges and Practical Solutions

Challenge: The PDF Contains Too Much Information

Solution: Define the audience first, then keep only the fields needed for that audience. A project sponsor may need milestones and risks, while a technician may need task instructions and assigned dates.

Challenge: The PDF Is Hard to Read on Screen

Solution: Use fewer columns, landscape orientation, and readable scaling. Add repeated headings so readers can understand each page without returning to the first page.

Challenge: The Report Becomes Outdated Quickly

Solution: Set a regular reporting point, such as every Friday afternoon. Update task progress and the status date immediately before exporting the PDF.

Challenge: Different People Need Different Views

Solution: Create separate outputs for separate decisions. A leadership summary, a delivery task list, and a resource view should not be forced into one crowded PDF.

Challenge: The Same Formatting Work Repeats Every Week

Solution: Save a custom view or reporting layout when your edition supports it. Keep the column order, filters, page settings, and heading choices consistent.

FAQs

Can I remove the Gantt chart without deleting project tasks?

Yes. Changing the active view only changes what appears on screen and in the exported PDF. Your tasks, dates, dependencies, resources, and progress values remain in the project. Select Task Sheet or another non-Gantt view before printing.

What is the best MS Project view for a PDF without the timeline?

Task Sheet is usually the best choice for a detailed task list. It keeps task names, dates, durations, and progress fields while removing the timeline. Use Resource Sheet for people and assignments, or a report view for executive summaries.

Why does my PDF still show the Gantt chart?

The active view may still be Gantt Chart, or the print settings may include a broader project view. Return to the View tab, select Task Sheet, and choose the current or active view in print preview. Then check the preview before saving.

Can I export only selected tasks?

Usually, you can filter or select the activities you need before printing. Apply a filter such as incomplete tasks, late tasks, or tasks within a date range. Confirm that the preview contains only the intended rows.

How do I make the PDF fit on fewer pages?

Remove unnecessary columns, use landscape orientation, reduce excessive margins, and choose a suitable page size. Keep the text readable. A slightly longer PDF is better than one with tiny type and clipped values.

Should I use a report instead of a task list?

Use a report when the audience needs a summary, trend, cost view, or milestone overview. Use Task Sheet when people need to inspect individual activities. Many teams benefit from creating both, with each PDF serving a different purpose.

Conclusion

To save Microsoft Project as a PDF without the Gantt chart, switch to Task Sheet or another non-Gantt view, choose the active view for printing, and review the preview before exporting. Then improve readability by limiting columns, selecting the right orientation, repeating headings, and checking page breaks.

The core problem is rarely the PDF format itself. The real issue is choosing a view that matches the reader’s question. A table can be better for task ownership, dates, and progress, while a timeline remains useful for sequencing and dependencies.

But here’s the truth: a clean report begins before export. When project information is structured consistently, you spend less time repairing layouts and more time discussing delivery decisions.

For teams that need a broader reporting workflow, ONES.com offers project management through ONES Project, knowledge management through ONES Wiki, Jira-compatible workflows, built-in reporting, custom fields, automation, and flexible deployment options. The right setup can make every status update easier to prepare and easier to understand.