DWG vs DWF: Drawing Files and Shared Views

DWG and DWF may contain views of the same design, but they usually serve different purposes. DWG is commonly the working drawing used by the designer. DWF is a published format used to distribute and review design information.

That difference affects what a recipient can do. A designer continuing a CAD drawing may need the source DWG and its supporting files. A stakeholder reviewing a published design may need a suitable DWF viewer instead. Asking for the wrong format can create unnecessary conversion work.

This guide explains how the formats fit a handover. It also explains why a published review file is useful without being a complete substitute for the original working drawing.

What a DWG provides

A DWG contains structured drawing objects. These can include geometry, layers, blocks, dimensions, text, and prepared layouts. Some drawings also contain three-dimensional objects or specialist application data. The working drawing can carry information beyond its visible sheet appearance.

That structure matters when another person needs to edit. They may need to change a block, update an attribute, revise geometry, or maintain references. A published view may show the result without providing the same source workflow.

Our DWG format guide explains the main contents. It also covers why the DWG can depend on other files that must accompany a complete design handover.

What a DWF provides

DWF stands for Design Web Format. Autodesk’s DWF collaboration documentation describes it as a compressed publishing format for CAD data. Depending on the source and publishing choices, it can carry two-dimensional and three-dimensional design information.

Think of it as a prepared review deliverable. The author selects and publishes the content that recipients should inspect. That can be useful when reviewers do not need the full editing environment or source drawing package.

The file’s usefulness depends on what was published. A DWF may contain a sheet set, model views, or other design information. Do not assume every DWF includes every sheet and object from the original project.

Working geometry and published content

The working DWG supports the author’s design process. It may contain construction objects, unused definitions, reference arrangements, and sheets still being developed. A recipient who needs to continue the work should ask for the agreed source package.

The published DWF is prepared for a different audience. It can focus on issued sheets or reviewable design views. This can make the handover easier to follow when the recipient only needs to inspect and comment.

A published file is still not automatically approved information. Read its title, revision, and issue status. A file prepared for an early review should not be treated as a final instruction merely because it opens in a viewer.

Viewing software is part of the handover

Before sending DWF, ask whether the recipient has a suitable viewer and can use the required review tools. Autodesk’s viewer comparison page lists Design Review and Autodesk Viewer among its viewing options. Check current platform and file support for the proposed route.

For DWG, the recipient needs an appropriate viewer or editor, depending on the task. Our free DWG viewer comparison helps identify a route that fits their device and review purpose.

Send a clear explanation with the file. State whether it is an editable source delivery or a published review package. The recipient should not have to discover the intended workflow by trying unrelated applications.

Sheets can be published as a set

A design project often has several sheets. Publishing them together can help reviewers see related information in one package. Plans, elevations, details, and schedules make more sense when their relationships are clear.

Autodesk’s publishing instructions describe assembling an electronic drawing set with selected sheets. The exact interface depends on the application and release. Review the selected sheet list before publishing.

Afterward, open the output and check its order and completeness. A successful publish operation can still create the wrong package if the author selected the wrong layouts. Inspect the title blocks and revision information on several sheets, not only the first one.

Three-dimensional information needs inspection too

Some published DWFs include 3D design content. This can help a reviewer understand how parts or building elements relate. However, a flat sheet does not become a complete 3D model simply because the output format can support one.

Check the views and model content that the author actually supplied. Start with an overall view, then inspect the feature relevant to the review. Keep the design’s dimensions and specifications available when a question needs more than a visual impression.

For DWG model review, see our guide to viewing a 3D DWG. The same habit applies to DWF: understand the contents before interpreting the tools available around them.

Comments and source edits are different actions

A review markup identifies an issue or asks a question. Changing the underlying wall position or part geometry changes the design. Keep that distinction clear when explaining what you have done to either file.

For each comment, name the sheet or view and the exact location. Use a short question that the author can answer. A note such as confirm opening width is more useful when it points to the intended opening and states the conflicting information.

Agree how review comments become resolved design changes. The responsible author usually needs to update the working source and issue a new deliverable. A marked published file alone may not show that the underlying design has been corrected.

Measurements need a known context

A viewer may offer measurements in a published design. Before using a result, confirm the relevant units and view context. Compare a known dimension and understand which geometry points the tool selects.

Do not confuse a sheet’s plotted appearance with the source model’s coordinate system. The published file may provide useful review data, but the reviewer still needs to interpret it correctly. If the tool and labelled dimension disagree, ask the author to clarify.

State the measured feature, points, and units in your note. The distance between two hole centres differs from the clearance between their edges. That detail matters more than whether the number came from a DWG or DWF viewer.

Publishing and conversion are not reversible guarantees

Creating DWF from a drawing is a publishing step. Reconstructing a complete working DWG from that published result is a different problem. Do not assume the source’s object structure, references, and specialist data can be restored exactly.

If you need to edit, ask for the DWG from the author. If you need to review, ask for a clear published package. Choosing the right deliverable at the start avoids unnecessary attempts to recover source information from review output.

Changing a filename extension does not convert either format. Use the application’s supported publish or export workflow. Preserve the original and verify the generated output before sending it to others.

File size and completeness are separate questions

Published design files can be convenient to distribute, especially when the recipient does not need the whole source package. However, smaller size is not evidence that all required review information is present.

Check the selected sheets, notes, model details, and revision. A compact file that omits the relevant detail is less useful than a larger complete package. Define the review scope first, then judge whether the published output meets it.

For source DWG delivery, make sure supporting references and images are included. A larger attachment containing only the main drawing can still be incomplete. The right package is determined by its contents and dependencies, not its size.

A practical handover example

Imagine a facilities manager needs to review a proposed office layout. A published package with the relevant plan and details may be enough. The manager can locate furniture, read notes, and raise questions without needing to modify CAD objects.

An engineer coordinating services in the same office may need editable geometry and references. That person should receive the agreed source DWG package and a reference view of the issued design. The two recipients need different deliverables even though the project is the same.

Tell each recipient the revision, issue status, and expected response. Ask them to confirm that they can see the required sheets or objects. This simple check turns format selection into a clear working handover.

Choose according to the next person’s job

Use DWG when the recipient needs the working CAD structure for an agreed editing or coordination task. Use DWF when a published design review fits the recipient’s tools and requirements. If a general document reader is preferred, our DWG versus PDF guide explains another review route.

Keep the source, published output, and comments clearly identified. Inspect the finished package before distributing it. A useful review file makes the intended revision easy to read, while a useful source delivery gives the next designer the information needed to continue the work.